 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| this is information on a product in full production. january 2015 docid023790 rev 13 1/87 1 m24sr64-y dynamic nfc/rfid tag ic with 64-kbit eeprom, nfc forum type 4 tag and i2c interface datasheet - production data features i 2 c interface ? two-wire i 2 c serial interface supports 1 mhz protocol ? single supply voltage: 2.7 v to 5.5 v contactless interface ? nfc forum type 4 tag ? iso/iec 14443 type a ? 106 kbps data rate ? internal tuning capacitance: 25 pf memory ? 8-kbyte (64-kbit) eeprom ? support of ndef data structure ? data retention: 200 years ? endurance: 1 million erase-write cycles ? read up to 246 bytes in a single command ? write up to 246 bytes in a single command ? 7 bytes unique identifier (uid) ? 128 bits passwords protection package ? 8-lead small-outline package (so8) ecopack2 ? ? tssop8 ecopack2 ? ? ufdfpn8 ecopack2 ? ? wfdfdn8 ecopack2 ?(a)(b) digital pad ? gpo: configurable general purpose output ? rf disable: activation/deactivation of rf commands description the m24sr64-y device is a dynamic nfc/rfid tag ic with a dual interface. it embeds an eeprom memory. it can be operated from an i 2 c interface or by a 13.56 mhz rfid reader or an nfc phone. the i 2 c interface uses a two-wire serial interface, consisting of a bidirectional data line and a clock line. it behaves as a slave in the i 2 c protocol. the rf protocol is compatible with iso/iec 14443 type a and nfc forum type 4 tag. tssop8 (dw) so8 (mn) ufdfpn8 (mc) wafer (sb12i) wfdfpn8 (mf) a. preliminary data for automotive grade (under qualification). b. package for automotive grade. www.st.com
contents m24sr64-y 2/87 docid023790 rev 13 contents 1 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.1 functional modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.1.1 i2c mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.1.2 tag mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.1.3 dual interface mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2 signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.1 serial clock (scl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2 serial data (sda) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3 antenna coil (ac0, ac1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.4 ground (vss) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.5 supply voltage (v cc ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.5.1 operating supply voltage v cc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.5.2 power-up conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.5.3 device reset in i2c mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.5.4 power-down conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.6 rf disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.7 general purpose output (gpo) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.7.1 session open configuratio n (gpo field = 0xx1 or 0x1x) . . . . . . . . . . . 14 2.7.2 wip writing in progress configuratio n (gpo field = 0xx2 or 0x2x) . . . 15 2.7.3 i 2 c answer ready configuration (gpo field = 0xx3) . . . . . . . . . . . . . . . 16 2.7.4 mip ndef message writing in progress configuration (gpo field = 0x3x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.7.5 int interrupt configuratio n (gpo field = 0xx4 or 0x4x) . . . . . . . . . . . . 18 2.7.6 state control configuration (gpo field = 0xx5 or 0x5x) . . . . . . . . . . . . 19 2.7.7 rf busy configuration (gpo field = 0x6x) . . . . . . . . . . . . . . . . . . . . . . . 20 3 m24sr64-y memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1 memory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1.1 file identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1.2 cc file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1.3 ndef file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.1.4 system file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.2 read and write access rights to the memory . . . . . . . . . . . . . . . . . . . . . . 25 docid023790 rev 13 3/87 m24sr64-y contents 5 3.2.1 state of the read and write access rights . . . . . . . . . . . . . . . . . . . . . . . 25 3.2.2 changing the read access right to ndef files . . . . . . . . . . . . . . . . . . . . 26 3.2.3 changing the write access right to ndef files . . . . . . . . . . . . . . . . . . . 27 3.3 access right life time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.4 ndef file passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.5 i2c password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.5.1 i2c password and i2c protect field of the system file . . . . . . . . . . . . . . . 28 4 communication mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.1 master and slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.2 m24sr64-y session mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.2.1 rf token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.2.2 i 2 c token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5 i2c and rf command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.1 structure of the command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5.2 i-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5.2.1 c-apdu: payload format of a command . . . . . . . . . . . . . . . . . . . . . . . . 32 5.2.2 r-apdu: payload format of a response . . . . . . . . . . . . . . . . . . . . . . . . 33 5.3 r-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 5.4 s-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5.5 crc of the i2c and rf frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 5.6 nfc forum type 4 tag protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 5.6.1 commands set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 5.6.2 status and error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.6.3 ndef tag application select command . . . . . . . . . . . . . . . . . . . . . . . . 38 5.6.4 capability container select command . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5.6.5 ndef select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 5.6.6 system file select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 5.6.7 readbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 5.6.8 updatebinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 5.7 iso/iec 7816-4 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 5.7.1 verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 5.7.2 change reference data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 5.7.3 enable verification requirement command . . . . . . . . . . . . . . . . . . . . . . 45 5.7.4 disable verification requirement command . . . . . . . . . . . . . . . . . . . . . 46 contents m24sr64-y 4/87 docid023790 rev 13 5.8 st proprietary command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 5.8.1 extendedreadbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 5.8.2 enablepermanentstate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 5.8.3 disablepermanentstate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.8.4 updatefiletype command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 5.8.5 sendinterrupt command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 5.8.6 statecontrol command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 5.9 specific rf command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.9.1 anticollision command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.9.2 rats command and ats response . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.9.3 pps command & response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 5.10 specific i2c command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5.10.1 geti2csession command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5.10.2 killrfsession command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 6 rf device operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 6.1 anticollision and device activation command set for the rf interface . . 56 6.2 open an rfsession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 6.3 close an rfsession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 6.4 applicative command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 7 i2c device operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 7.1 i2c communication protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 7.2 start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 7.3 stop condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 7.4 i2c timeout on start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 7.5 i2c timeout on clock period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 7.6 acknowledge bit (ack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 7.7 data input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 7.8 i2c device address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 7.9 i2c frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 7.9.1 example of i2c frame commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 7.10 open an i2c session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 7.11 close the i2c session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 docid023790 rev 13 5/87 m24sr64-y contents 5 8 functional procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 8.1 selection of an ndef message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 8.2 reading of an ndef message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 8.3 reading a locked ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 8.4 locking an ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 8.5 unlocking an ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 8.6 reaching the read-only state for an ndef file . . . . . . . . . . . . . . . . . . . . . 64 8.7 changing an ndef password procedure . . . . . . . . . . . . . . . . . . . . . . . . . 64 8.8 changing a file type procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 9 uid: unique identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 10 maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 11 i2c dc and ac parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 11.1 i2c timing measurement condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 12 gpo parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 13 rf electrical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 14 package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 14.1 mechanical data for the so8n package . . . . . . . . . . . . . . . . . . . . . . . . . . 77 14.2 mechanical data for the tssop8 package . . . . . . . . . . . . . . . . . . . . . . . 78 14.3 mechanical data for the ufdfpn8 package . . . . . . . . . . . . . . . . . . . . . . 79 14.4 mechanical data for the wfdpn8 package . . . . . . . . . . . . . . . . . . . . . . . 81 15 part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 16 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 list of tables m24sr64-y 6/87 docid023790 rev 13 list of tables table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 table 2. functional modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 table 3. file identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 4. cc file layout for 1 ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 5. ndef file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 6. field list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 7. details about the gpo field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 8. details about the rf session field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 9. details about the st reserved field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 10. details about the rf enable field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 11. read access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 12. write access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 13. rf and i2c command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 table 14. i-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 15. pcb field of the i-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 16. c-apdu format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 17. r-apdu format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 18. r-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 19. r-block detailed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 20. s-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 21. s-block detailed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 table 22. command set overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 23. status code of the m24sr64-y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 24. error code of the m24sr64-y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 25. c-apdu of the ndef tag applic ation select command . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 26. r-apdu of the ndef tag applic ation select command . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 27. c-apdu of the capability container sele ct command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 table 28. r-apdu of the capability container sele ct command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 table 29. c-apdu of the ndef select comman d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 table 30. r-apdu of the ndef select comman d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 31. c-apdu of the system file sele ct command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 32. r-apdu of the system file sele ct command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 33. c-apdu of the readbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 34. r-apdu of the readbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 35. c-apdu of the updatebinary comma nd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 36. r-apdu of the updatebinary comma nd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 37. verify command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 table 38. r-apdu of the verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 39. change reference data command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 40. r-apdu of the change reference data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 table 41. enable verification requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 table 42. r-apdu of the enable verification requirement co mmand. . . . . . . . . . . . . . . . . . . . . . . . 46 table 43. disable verification requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 table 44. r-apdu of the disable verification requirement command . . . . . . . . . . . . . . . . . . . . . . . 47 table 45. c-apdu of the extendedreadbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 46. r-apdu of the extendedreadbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 table 47. enablepermanentstate command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 table 48. r-apdu table of the enablepermanentstate comman d . . . . . . . . . . . . . . . . . . . . . . . . . . 48 docid023790 rev 13 7/87 m24sr64-y list of tables 7 table 49. disablepermanentstate command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 table 50. r-apdu of the disablepermanentstate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 table 51. updatefiletype command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 table 52. r-apdu of the updatefiletype co mmand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 table 53. sendinterrupt command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 table 54. r-apdu of the sendinterrupt command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 table 55. statecontrol command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 table 56. r-apdu of the statecontrol command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 table 57. commands issues by the rf host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2 table 58. rats command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 59. conversion from fdsi to fsd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 60. ats response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 61. pps command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 table 62. ascending and descending data rate coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 table 63. pps response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 table 64. specific i2c commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 table 65. geti2csession command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 table 66. killrfsession command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 table 67. i2c device address format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 table 68. i 2 c frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 table 69. i2c host to m24sr64-y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 table 70. m24sr64-y to i2c host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 table 71. uid format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 table 72. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 table 73. i 2 c operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 table 74. ac test measurement conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 table 75. input parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 table 76. i 2 c dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 table 77. i 2 c ac characteristics (400 khz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 78. i 2 c ac characteristics (1 mhz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 79. device select code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 80. gpo timings measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 81. default operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 table 82. rf characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 table 83. so8n - 8-lead plastic small outline, 150 mils body width, package data . . . . . . . . . . . . . . 77 table 84. tssop8 - 8-lead thin shrink small outline, 16 9 mils width, package data . . . . . . . . . . . . . 78 table 85. ufdfpn8 - 8- lead ultra thin fine pitch du al flat package, no lead, package data . . . . . . . 80 table 86. wfdfpn8 8-lead thin fine pitch dual flat package no lead mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 table 87. ordering information scheme for packaged devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 table 88. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 list of figures m24sr64-y 8/87 docid023790 rev 13 list of figures figure 1. m24sr64-y block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 2. 8-pin package connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 3. gpo configured as session open (gpo field = 0x x1 or 0x1x) . . . . . . . . . . . . . . . . . . . . . 14 figure 4. gpo configured as wip (gpo fi eld = 0xx2 or 0x2x). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 5. gpo configured as i 2 c answer ready (gpo field = 0xx3) . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 6. gpo configured as mip (gpo field = 0x3x). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 figure 7. gpo configured as int (gpo fi eld = 0xx4 or 0x4x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 figure 8. gpo configured as state control (gpo field = 0x x5 or 0x5x). . . . . . . . . . . . . . . . . . . . . . 19 figure 9. gpo configured as rf busy (gpo field = 0x6x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 figure 10. changing the read access right to an ndef file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 11. changing the write access right to an ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 figure 12. command and response exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 figure 13. i2c timeout on start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 figure 14. ndef tag application select comm and . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 figure 15. ac test measurement i/o waveform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7 figure 16. i 2 c ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 figure 17. maximum rbus value with fc = 400 khz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 figure 18. maximum rbus value with fc = 1 mhz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 figure 19. i2c bus protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 figure 20. so8n - 8-lead plastic small outline, 150 mils body width, package outline . . . . . . . . . . . . 77 figure 21. tssop8 - 8-lead thin shrink small outline, pack age outline . . . . . . . . . . . . . . . . . . . . . . . . 78 figure 22. ufdfpn8 - 8-lead ultra thin fine pitch dual flat package, no lead, 2x3 mm, package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 figure 23. wfdfpn8 8-lead thin fine pitch dual flat package no lead package outline . . . . . . . . . . . 81 docid023790 rev 13 9/87 m24sr64-y functional description 20 1 functional description the m24sr64-y device is a dynamic nfc/rfid tag that can be accessed either from the i 2 c or the rf interface. the rf and i 2 c host can read or write to the same memory, that is why only one host can communicate at a ti me with the m24sr64-y. the management of the interface selection is controlle d by the m24sr64-y device itself. the rf interface is based on the iso/iec 14443 type a standard. the m24sr64-y is compatible with th e nfc forum type 4 tag specifications and supports all corresponding commands. the i 2 c interface uses a two-wire serial interface consisting of a bidirectional data line and a clock line. the devices carry a built-in 4-bit dev ice type identifier code in accordance with the i2c bus definition. the device behaves as a slave in the i 2 c protocol. figure 1 displays the block diagram of the m24sr64-y device. figure 1. m24sr64-y block diagram 0 6 9 6 x s s o \ y r o w d j h i r u , & l q w h u i d f h 5 ) l q w h u i d f h e d v h g r q , 6 2 , ( & 7 \ s h $ v w d q g d u g , & l q w h u i d f h 9 9 9 & & $ & $ & 6 & / * 3 2 6 ' $ * 1 ' 3 r z h u p d q d j h p h q w x q l w h / ? ???? u ? h? ? u u}?? $ q d o r j ) u r q w h q g e d v h g r q , 6 2 , ( & 7 \ s h $ v w d q g d u g , q w h u q d o w x q l q j f d s d f l w d q f h 1 ) & ) r u x p 7 \ s h 7 d j s u r w r f r o 1 ) & b , & l q w h u i d f h ' l j l w d o x q l w 5 ) g l v d e o h functional description m24sr64-y 10/87 docid023790 rev 13 figure 2. 8-pin package connections 1. see package mechanical data section for packa ge dimensions, and how to identify pin 1. 1.1 functional modes the m24sr64-y has two functional modes ava ilable. the difference between the modes lies in the power supply source (see table 2 ). 1.1.1 i 2 c mode m24sr64-y is powered by v cc . the i 2 c interface is connected to the m24sr64-y. the i 2 c host can communicate with the m24sr64-y device. 1.1.2 tag mode the m24sr64-y is supplied by the rf fiel d and can communicate with an rf host (rfid reader or an nfc phone). the user memory can only be accessed by the rf commands. table 1. signal names signal name function direction sda serial data i/o scl serial clock input ac0, ac1 antenna coils - v cc supply voltage - vss ground - gpo interrupt output (1) 1. an external pull-up > 4.7 k ? is required. open drain output rf disable disable the rf communication (2) 2. an external pull-down is required when the voltage on v cc is above its por level. input 0 6 9 6 ' $ 6 & / * 3 2 $ & $ & 9 6 6 5 ) g l v d e o h 9 & & table 2. functional modes modes supply source comments i 2 c mode v cc the i 2 c interface is available tag mode rf field only the i 2 c interface is disconnected dual interface mode rf field or v cc both i 2 c and rf interfaces are available docid023790 rev 13 11/87 m24sr64-y functional description 20 1.1.3 dual interface mode both interfaces, rf and i 2 c, are connected to the m24sr64-y and both rf or i 2 c host can communicate with the m24sr64-y device. the power supply and the access management are carried out by the m24sr64-y itself. for further details, please refer to the token mechanism chapter. signal descriptions m24sr64-y 12/87 docid023790 rev 13 2 signal descriptions 2.1 serial clock (scl) this input signal is used to strobe all data in and out of the device. in applications where this signal is used by slave devices to synchronize the bus to a slower clock, the bus master must have an open drain output, and a pull-up re sistor must be connected from serial clock (scl) to v cc . ( figure 17 indicates how the value of the pull-up resistor can be calculated). in most applications, though, this method of synchronization is not employed, and so the pull-up resistor is not necessary, provided th at the bus master has a push-pull (rather than open drain) output. 2.2 serial data (sda) this bidirectional signal is used to transfer dat a in or out of the device. it is an open drain output that may be wire-or'ed with other open drain or open collector signals on the bus. a pull-up resistor must be connect ed from serial data (sda) to v cc . ( figure 17 indicates how the value of the pull-up resistor can be calculated). 2.3 antenna coil (ac0, ac1) these inputs are used to connect the device to an external coil exclusively. it is advised not to connect any other dc or ac path to ac0 or ac1. when correctly tuned, the coil is used to access the device using nfc forum type 4 commands. 2.4 ground (v ss ) v ss , when connected, is the reference for the v cc supply voltage for all pads, even ac0 and ac1. 2.5 supply voltage (v cc ) this pin can be connected to an external dc supply voltage. note: an internal voltage regulator allows the external voltage applied on v cc to supply the m24sr64-y. 2.5.1 operating supply voltage v cc prior to selecting the m24sr64-y and issuing instructions to it, a valid and stable v cc voltage within the specified [v cc (min), v cc (max)] range must be applied. to maintain a stable dc supply voltage, it is recommended to decouple the v cc line with suitable capacitors (usually of the order of 10 nf and 100 pf) close to the v cc /v ss package pins. this voltage must remain stable and valid unt il the end of the transmission of the instruction and, for a writing instruction (upd atebinary, changereferencedata, docid023790 rev 13 13/87 m24sr64-y signal descriptions 20 enableverificationrequirement, disableverifi cationrequirement, enablepermanentstate, disablepermanentstate, unt il the completion of the internal i2c write cycle (t w ). 2.5.2 power-up conditions when the power supply is turned on, v cc rises from v ss to v cc . the v cc rise time must not vary faster than 1v/s. 2.5.3 device reset in i2c mode in order to prevent inadvertent write operations during power-up, a power-on reset (por) circuit is included. at power -up (continuous rise of v cc ), the m24sr64-y does not respond to any i2c instruction until v cc has reached the power-on reset threshold voltage (this threshold is lower than the minimum v cc operating voltage defined). when v cc passes over the por threshold, the device is reset and enters the standby power mode. however, the device must not be accessed until v cc has reached a valid and stable v cc voltage within the specified [v cc (min), v cc (max)] range. in a similar way, during power-down (continuous decrease in v cc ), as soon as v cc drops below the power-on reset threshold voltage, the m24sr64-y stops responding to any instruction sent to it. 2.5.4 power-down conditions during power-down (continuous decay of v cc ), the m24sr64-y must be in standby power mode (mode reached after decoding a stop condition, assuming that there is no internal operation in progress). 2.6 rf disable this input signal is used to disable the rf communication. when the voltage on the v cc pin is below the por level or not connected, an internal pull-down resistor is connected on this pad. thus, the rf disable pad is maintained to the low level and the rf analog front end is activated. when the voltage on the v cc pin is higher than the por level, the i2c host shall set this pin to enable or disable the rf communication. in dual interface mode, rf disable must not be left floating. 2.7 general purpos e output (gpo) the gpo pad is an open drain pad and a external pull-up resistor shall be connected to it. this pad is a configurable output signal. on delivery, gpo is configured as session opened. its behavior is consistent with the i 2 c or rf session activated and with the mode chosen by the user. the gpo pad is enable when an rf or an i 2 c session is open. when neither an rf nor an i 2 c session is open, the gpo is high impedance. signal descriptions m24sr64-y 14/87 docid023790 rev 13 the user can select one of these configurations (a) : ? sessionopen: an rf or i 2 c session is ongoing. ? mip (ndef message updating in progress): the rf host is writing an ndef length different from 0x0000. this mode can be used to detect when the rf host changes the ndef message as defined by the nfc forum. ? wip (writing in progress): the m24sr64-y is executing a writing operation. ? int (interrupt): the i 2 c or rf host can force the m24sr64-y to send a negative pulse on the gpo pin. ? i 2 c ready response: an i 2 c response is ready to be read by the i2c host. ? state mode: the i 2 c or rf host can control the state of the gpo pad during the rf session. ? rf busy: an rf host is communicating with the m24sr64-y. 2.7.1 session open configuratio n (gpo field = 0xx1 or 0x1x) when the gpo is configured as "session open" , it goes to the low state when an rf or i 2 c session is ongoing (see figure 3 ). an rf session is taken when m24sr64-y receives a valid sele ct application. the session is released after m24sr64-y has received a valid deselect command, if m24sr64-y has received a kill rf session command in i 2 c or when the rf field became off. an i 2 c session is taken when m24sr64-y receiv es a valid get session command or a valid kill rf session command. the session is rel eased after m24sr64-y has received a valid deselect command or after a power off. gpo is driven low after a delay (1) or (3) when the session is open. gpo is released after a delay (2) or (4) when the session is released. figure 3. gpo configured as session open (gpo field = 0xx1 or 0x1x) 1. cmdeoftogplow (rf command end of frame to gporf session pad low) 2. cmdeoftogphz (rf command end of frame to gporf session pad hz) 3. cmdstptogplow (i2c command stop to gpo low) 4. answerlblbtogphz (i2c answer last bit of last byte to gpo hz) a. see table 80 for more details. d ^??e s? z & ^ ??]}v /? ^ ??]}v z & ^ ??]}v ^ ??]}v ' w k ? ^ ??]}v k? v <]oo? ??]}v }? ' ?? ??]}v v?]}oo]?]}v ? e & ? o ? ? o ? ? o ? ~? ~e ~ ~? docid023790 rev 13 15/87 m24sr64-y signal descriptions 20 2.7.2 wip writing in pr ogress configuration (gpo field = 0xx2 or 0x2x) when the gpo is configured as "wip", it goes to the low state during an i 2 c or rf writing operation. during an rf or i 2 c session, when m24sr64-y updates a file, gpo is driven low after a delay (1) or (3) following the beginning of the correspondent updatebinary command execution. gpo will remain low during the writing time (2) or (4), before being released. figure 4. gpo configured as wip (gpo field = 0xx2 or 0x2x) 1. cmdstptogplow (i2c command stop to gpo low) 2. writing time duration 3. cmdeoftogplow (rf command end of frame to gpo low) 4. writing time duration d ^?? s? h?? }uuv v? }?z ? }uuv ~? }? ~e z & }? /? zvv o ' w k ? t / w v }( ?]?]vp }? ??]}v ~ }? ~? signal descriptions m24sr64-y 16/87 docid023790 rev 13 2.7.3 i 2 c answer ready configur ation (gpo field = 0xx3) when the gpo is configured as i 2 c answer ready, it goes to the low state when the m24sr64-y has finished to treat the i 2 c command and is ready to send the i 2 c response. during an i 2 c session, after receiving a valid i 2 c command, gpo pin is driven low after a delay when m24sr64-y is ready to deliver a response on the i 2 c bus. gpo is released when m24sr64-y receives a new command. figure 5. gpo configured as i 2 c answer ready (gpo field = 0xx3) d ^??? se k? v ^ ??]}v /? zvv o ' w k ? /? v? ? ? ? v? /? }uuv d?e ^ z?? ? ??}v? v? /? }uuv d?e ^ z?? ? ??}v? v? /? }uuv d?e ^ z?? ? ??}v? docid023790 rev 13 17/87 m24sr64-y signal descriptions 20 2.7.4 mip ndef messa ge writing in pr ogress configuration (gpo field = 0x3x) when the gpo is configured as mip, its state goes to the low state when the rf host writes the ndef length to another value than 0x0000. during an rf session, when m24sr64-y changes an ndef file and updates the ndef length with a value different from 0x0000, gpo is driven low after a delay (1) following the beginning of the correspondent updatebinary command execution. gpo will remain low during the writin g time (2), before being released. figure 6. gpo configured as mip (gpo field = 0x3x) 1. cmdeoftogplow (rf command end of frame to gpo low) 2. writing time duration d ^??? s? v? }?z ? }uuv h?? ?z e & o vp?z ja ? z & zvv o ' w k ? d / w d?e ^ z?? ? ??}v? ~ ~? signal descriptions m24sr64-y 18/87 docid023790 rev 13 2.7.5 int interrupt configurat ion (gpo field = 0xx4 or 0x4x) the i 2 c or rf host can send a negative pulse on the gpo pad. the gpo pad goes to the low state at the end of the command and goes to the high state at the end of the m24sr64- y response. during an rf or i 2 c session, when m24sr64-y receives a valid interrupt command, m24sr64-y gpo pin is driven low after (1) or (3) for a duration of (4) in rf, or after responding in i2c (2). then gpo pin is released. figure 7. gpo configured as int (gpo field = 0xx4 or 0x4x) 1. cmdstptogplow (i2c command stop to gpo low) 2. after newcmdlbfb (new i2c comma nd last bit of first byte) or after answerlbfb (i2c answer last bit of first byte) 3. cmdeoftogplow (rf command end of frame to gpo low) 4. gpo pulse duration d ^?? s? ^ v /v? ???? ' w k ? / e d v? }?z ? }? ??]}v z & }? /? zvv o d?e ^ z?? ? ??}v? ~ }? ~? ~? ~e docid023790 rev 13 19/87 m24sr64-y signal descriptions 20 2.7.6 state control configurati on (gpo field = 0xx5 or 0x5x) when the gpo is configured as state control, the i 2 c or rf host can control the state of the gpo by sending a dedicated command. during an rf or i 2 c session, the m24sr64-y can control the gpo pin. after receiving a valid set gpo command, gpo pin is driven low after a delay (1) or (3). gpo will be released after a valid reset command or after a power off. figure 8. gpo configured as state control (gpo field = 0xx5 or 0x5x) 1. cmdstptogplow (i2c set gpo command stop to gpo low) 2. cmdstptogphz (i2c reset gpo command stop to gpo hz) 3. cmdeoftogplow (rf set gpo command end of frame to gpo low) 4. cmdeoftogphz (rf reset gpo command end of frame to gpo hz) 0 6 9 5 h v h w * 3 2 f r p p d q g $ q \ r w k h u f r p p d q g 6 h w * 3 2 f r p p d q g 5 ) r u , e & f k d q q h o * 3 2 d v 6 w d w h & r q w u r o r u r u signal descriptions m24sr64-y 20/87 docid023790 rev 13 2.7.7 rf busy configurat ion (gpo field = 0x6x) when the gpo is configured as rf busy, the gpo goes to the low state when the m24sr64-y is processing an rf command or when an rfsession is ongoing. when an rf field is present, gpo is driven low after a delay (1) when m24sr64-y detects the first command. if the rf session is ongo ing and m24sr64-y receives a not-supported command, gpo remains low. it will be released only at the end of the rf session, after (2). figure 9. gpo configured as rf busy (gpo field = 0x6x) 1. cmdsoftogplow (rf command start of frame to gpo low) 2. cmdeoftogphz (rf command end of frame to gpo hz) d ^?? s? z & }uuv v}? ???}?? ^ v? z ? ? ^ v? z ? z & }uuv z & zvv o ' w k ? z & ?? ^~ ^ ~ ~? ~ ~? docid023790 rev 13 21/87 m24sr64-y m24sr64-y memory management 28 3 m24sr64-y memory management 3.1 memory structure the m24sr64-y supports the ndef tag application as defined in the nfc forum type 4 tag. the m24sr64-y is composed of three files: ? one capability container file ? one ndef file ? one system file: this is an st-proprietary file the system file contains some information on the configuration of the m24sr64-y device. the cc file gives some information about t he m24sr64-y itself and the ndef file. the ndef file contains the user data. 3.1.1 file identifier the file identifier is the value used in the select command to select a file. 3.1.2 cc file layout the cc file gives some information about the m24sr64-y and the ndef file. this file is a read-only file for the rf or i2c host and cannot be modified by issuing a write command. the t field, read access and write access fiel ds can be changed by the rf or i2c host by issuing a specific process (refer to section 8: functional procedures ). table 3. file identifier file identifier meaning 0xe101 system file 0xe103 cc file 0x0001 ndef file m24sr64-y memory ma nagement m24sr64-y 22/87 docid023790 rev 13 3.1.3 ndef file layout the ndef file contains the ndef message wh ich contains the user data. the rf host or the i2c host can read and write data inside the file. the first two bytes named ndef message length define the size of the ndef message. the ndef message length shall be managed by the application and the m24sr6 4-y device does not check if its value is relevant vs the data written by the rf or i2c host. the m24sr64-y device uses the ndef message length, e. g. the standard read can be processed only inside the ndef message; otherwise, the m24sr64-y device returns an error code. for more details about the read command, refer to section 5.6.7: readbinary command . table 4. cc file layout for 1 ndef file file offset meaning value comments 0x0000 number of bytes of cc file 0x000f 15 bytes 0x0002 mapping version (1) 1. according to the reader. 0x20 or 0x10 v 2.0 or v 1.0 0x0003 maximum number of bytes that can be read 0x00f6 246 bytes 0x0005 maximum number of bytes t hat can be written 0x00f6 246 bytes 0x0007 ndef file control tlv 0x04 (2) 2. delivery state. t field 0x0008 0x06 l field 0x0009 0x0001 fileid 0x000b 0x2000 maximum ndef file size 0x000d 0x00 (2) read access 0x000e 0x00 (2) write access docid023790 rev 13 23/87 m24sr64-y m24sr64-y memory management 28 3.1.4 system file layout the system file specifies the co nfiguration of the m24sr64-y. table 6 lists the different fields. table 5. ndef file layout file offset byte 0 byte 1 byte 2 byte 3 0x0000 ndef message length user data user data 0x0004 user data user data user data user data ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 0x1ffc ... ... ... user data table 6. field list file offset field name number of bytes read access write access delivery state (1) 1. the delivery state for all passwords = 0x00000000000000000000000000000000. 0x0000 length system file 2 i2c or rf - 0x0012 0x0002 i2c protect 1 i2c or rf i2c (2) 2. the access is granted when the field i2c protect is set to the state unprotected or when the right i2c password was correctly received (see section 3.5: i2c password ). 0x01 0x0003 i2c watchdog 1 i2c or rf i2c (2) 0x00 0x0004 gpo 1 i2c or rf i2c (2) 0x11 0x0005 st reserved 1 i2c or rf i2c (2) 0x00 0x0006 rf enable 1 i2c or rf i2c (2) 0x xxxx xxx1 (3) 3. refer table 10 . 0x0007 ndef file number (rfu) 1 i2c or rf none 0x00 0x0008 uid 7 i2c or rf none 0x0284 xx xx xx xx xx or 0x028c xx xx xx xx xx (4) (5) 4. x values are defined by st to insure uid unicity. 5. automotive grade 0x000f memory size 2 i2c or rf none 0x1fff 0x0011 product code 1 i2c or rf none 0x84 or 0x8c (5) m24sr64-y memory ma nagement m24sr64-y 24/87 docid023790 rev 13 table 7. details about the gpo field file offset b7 b6-b4 b3 b2-b0 0x0004 rfu when an rf session is open: 0b000: high impedance 0b001: session opened 0b010: wip 0b011: mip 0b100: interrupt 0b101: state control 0b110: rf busy 0b111: rfu rfu when an i2c session is open: 0b000: high impedance 0b001: session opened 0b010: wip 0b011: i2c answer ready 0b100: interrupt 0b101: state control 0b110: rfu 0b111: rfu table 8. details about the rf session field file offset b7 b6-b4 b3-b0 0x0004 rfu when an rf session is open: 0b001: session opened rfu docid023790 rev 13 25/87 m24sr64-y m24sr64-y memory management 28 table 9 gives some details about the st reserved field. table 10 gives some details about the rf enable field. 3.2 read and write access rights to the memory an ndef file can be locked for read or write accesses. it is also protected by a 128-bit password that the host shall present before accessing the ndef file. there are two 128-bit passwords, one for the read access and the other one for the write access. an ndef file can be permanently locked for read or write accesses. thus, the host cannot access the ndef file. the read password shall be sent to the m24sr64-y device before reading a read-locked ndef file. the write password shall be present on the m24s r64-y device before wr iting a write-locked ndef file. the write password shall be sent to change the read or write access. the read or write access right is defined for the ndef file. 3.2.1 state of the read and write access rights two bytes in the cc file are used to define the read and write access rights to the ndef file. for more details, refer to section 3.1.2: cc file layout . table 9. details about the st reserved field file offset b7-b0 0x0005 0x00 table 10. details about the rf enable field file offset b7 b6-b4 b3 b2-b1 b0 0x0006 0: the rf field is off (1) 1: the rf field is on (1) 1. this field is written by the m24sr64-y. rfu 0: the rf disable pad is at low state (1) 1: the rf disable pad is at high state (1) rfu 0: the m24sr64-y does not decode the command received from the rf interface 1: the m24sr64-y decodes the comma nd received from the rf interface m24sr64-y memory ma nagement m24sr64-y 26/87 docid023790 rev 13 the state 0xff and 0xfe cannot be changed by using the read or write passwords. 3.2.2 changing the read access right to ndef files the state diagram on figure 10 shows how to change the access right to read an ndef file. figure 10. changing the read access right to an ndef file 1. see the procedure to lock the read access ( section 8.4: locking an ndef file ). 2. see the procedure to unlock the read access ( section 8.5: unlocking an ndef file ). 3. see the procedure to permanently lock the read access ( section 8.6: reaching the read-only state for an ndef file ). 4. proprietary state, not defined by nfc forum type 4 tag. table 11. read access right value meaning 0x00 read access without any security 0x80 locked (1) 1. the read password shall be sent before reading in the ndef file. 0xfe read not authorized table 12. write access right value meaning 0x00 write access without any security 0x80 locked (1) 1. the write password shall be sent before writing in the ndef file. 0xff write not authorized d ^?? se ? ?? ~e ? & ~e >}l ?z e & (]o ~ hvo}l ?z e & (]o ~? w ?uv v?o? vo}l ?z e & (]o w ?uv v?o? o}l ?z e & (]o ~? docid023790 rev 13 27/87 m24sr64-y m24sr64-y memory management 28 3.2.3 changing the write access right to ndef files the state diagram on figure 11 shows how to change the write access right to an ndef file. figure 11. changing the write access right to an ndef file 1. see the procedure to lock the write access. 2. see the procedure to unlock the write access. 3. see the procedure to permanently lock the write access ( section 8.6: reaching the read-only state for an ndef file ). 4. proprietary state, not defined by nfc forum type 4 tag. 3.3 access right life time the access right life time is validated while the nd ef file is selected or until the end of the rf or i2c session. once the read or write acce ss right is granted, the host can send one or more readbinary or updatebinary commands. at the end of a session or when the host selects another file, the read and write access rights are initialized. 3.4 ndef file passwords the ndef file passwords protect the read or write access from an rf or i2c interface from/to an ndef file. two ndef file passwords are av ailable for each ndef file: ? read password ? write password the length of a password is 128 bits (16 bytes). d ^?? se ? ?? ~e ? & & >}l ?z e & (]o ~ hvo}l ?z e & (]o ~? w ?uv v?o? vo}l ?z e & (]o w ?uv v?o? o}l ?z e & (]o ~? m24sr64-y memory ma nagement m24sr64-y 28/87 docid023790 rev 13 3.5 i 2 c password the i2c password can be sent only by the i2c host. it activates the superuser rights. the i2c host with the superuser rights can: ? access the ndef file regardless of the right access and without sending the ndef file passwords. ? change the access rights regardless of the current state. the length of the i2c password is 128 bits (16 bytes). 3.5.1 i2c password and i2c prot ect field of th e system file the i2c protect field in the system file can be set to: ? 0x00: the i2c host has the superuser righ t access without sending the i2c password ? 0x01: the i2c host has the superuser right access after sending the i2c password for more details about the system file layout, refer to section 3.1.4: syst em file layout . docid023790 rev 13 29/87 m24sr64-y communication mechanism 76 4 communication mechanism this chapter describes the principle of communication between an rf or an i 2 c host and the m24sr64-y device. 4.1 master and slave the m24sr64-y acts as a slave device on either the i 2 c-bus or the rf channel and therefore waits for a command from the i 2 c master or the rf host before sending its response. the rf host shall generate the rf field and the rf commands. the i 2 c host shall supply the m24sr64-y through the v cc pin and shall generate the i 2 c clock on the scl pad. 4.2 m24sr64-y session mechanism the m24sr64-y is a dynamic nfc/rfid tag which can be accessed either from the rf or i 2 c interface. the m24sr64-y implements a token system. this token has two possible values, rf or i 2 c. when the token exists and is as signed to one interface (rf or i 2 c), the m24sr64-y cannot communicate with the other host. 4.2.1 rf token the token is given to the rf interface once t he anticollision is done. the release condition can be either an rf field cut-off, or the reception of the command deselect, or when the i2c host sends th e killrfsession. 4.2.2 i 2 c token the token is given to the i 2 c interface when the i 2 c host has sent the co rrect device select. the release condition can be either a power down condition on v cc pin or the reception of a command deselect from the i 2 c host, after which m24sr64-y goes in standby power mode. i2c and rf command sets m24sr64-y 30/87 docid023790 rev 13 5 i2c and rf command sets the command sets of the m24s r64-y can be split in differ ent command families. most commands are common between the rf and the i2c interface. some commands are specific to the rf interface and some others ar e specific to the i2c in terface. this section describes the m24sr64-y command sets that can be issued by the rf or the i2c host. there are th ree command families: ? the nfc forum type 4 tag command set ? the iso/iec 7816-4 command set ? the proprietary command set the nfc forum type 4 tag command set and the iso/iec 7816-4 command set use the i- block format. for more details about the i-block format, refer to section 5.2: i-block format . two other command formats exist: ? the commands using the r-block format ? the commands using the s-block format for more details about these formats, refer to the corresponding sections: section 5.3: r- block format and section 5.4: s-block format . this section gives a brief description of the rf and i2c host common commands. the format of these command se ts is the i-block format. table 13 lists the rf and i2c command sets. table 13. rf and i2c command sets family command set command name class byte instruction code brief description nfc forum type 4 tag ndef tag application select 0x00 0xa4 ndef tag application select cc select 0x00 0xa4 select the cc file ndef select 0x00 0xa4 select the ndef file system select 0x00 0xa4 select the system file readbinary 0x00 0xb0 read data from file updatebinary 0x00 0xd6 write or erase data to a ndef file iso/iec 7816-4 verify 0x00 0x20 checks the right access of a ndef file or sends a password changereferencedata 0x00 0x24 change a read or write password enableverificationr equirement 0x00 0x28 activate the password security disableverificationrequirement 0x00 0x26 disable the password security docid023790 rev 13 31/87 m24sr64-y i2c and rf command sets 76 5.1 structure of the command sets the exchange of data between the rf or the i2c host and the m24sr64-y uses three kinds of data formats, called blocks: ? i-block: to exchange the command and the response ? r-block: to exchange positive or negative acknowledgment ? s-block: to use either the deselect command or the frame waiting extension (wtx) command or response this section describes the structure of the i-bl ock, r-block and s-block. this format is used for the application command set. 5.2 i-block format the i-block is used to exchange data between the rf or the i2c host and the m24sr64-y. it is composed of three fields. table 14 details the i-block format. st proprietary enablepermanentstate 0xa2 0x28 enables the read only or write only security state st proprietary extendedreadbinary 0xa2 0xb0 read data from file table 13. rf and i2c command sets (continued) family command set command name class byte instruction code brief description table 14. i-block format name sod payload eod pcb did 0 crc length 1 byte 1 byte 1 to 251 bytes 2 bytes pcb field did field (optional) rf or i2c host to m24sr64-y: c-apdu m24sr64-y to rf or i2c host: r-apdu 2 crc bytes i2c and rf command sets m24sr64-y 32/87 docid023790 rev 13 when the rf or i2c host sends a command to the m24sr64-y the format of the payload is the c-apdu. when the m24sr64-y sends a command to the rf or i2c host, the format of the payload is the r-apdu. 5.2.1 c-apdu: payload format of a command the c-apdu format is used by the rf or the i2c host to send a command to the m24sr64- y. table 16 describes its format. table 15. pcb field of the i-block format b7-b6b5b4b3b2b1b0 0b00 0 0 x 0 1 x i-block rfu must be set to 0 did field, if bit is set must be set to 0 must be set to 1 block number table 16. c-apdu format name payload field cla ins p1 p2 lc data le length 1 byte 1 byte 1 byte 1 byte 1 byte lc byte 1 byte class byte 0x00: standard command 0xa2: st command instruction byte param byte 1 param byte 2 number of bytes of the data field data bytes number of bytes to be r ead in the m24sr64-y memory docid023790 rev 13 33/87 m24sr64-y i2c and rf command sets 76 5.2.2 r-apdu: payload format of a response the m24sr64-y uses the i-block format to reply to a command which used the i-block format. this format is described in table 17 . 5.3 r-block format the r-block is used to convey positive or neg ative acknowledgment between the rf or i2c host and the m24sr64-y. there are two kinds of r-blocks: ? r(ack): the acknowledgement block sent by the rf or i2c host or by the m24sr64-y ? r( nak ): the non-acknowledgement block sent by the rf or i2c host or by the m24sr64-y table 17. r-apdu format name payload field data (optional) sw1 sw2 length le byte 1 byte 1 byte data status byte 1 status byte 2 table 18. r-block format pcb crc r(ack) without the did field: 0xa2 or 0xa3 r(ack) with the did field: 0xaa or 0xab r(nak) without the did field: 0xb2 0xb3 r(nak) with the did field: 0xba 0xbb 2 crc bytes i2c and rf command sets m24sr64-y 34/87 docid023790 rev 13 5.4 s-block format the s-block is used to exchange control information between a reader and a contactless tag. there are two requests using the s-block format: ? s(des): the deselect command ? s(wtx): the waiting frame extension command or response. a waiting time extension request occurs, in rf or i 2 c, when the operating time needed by m24srxx is greater than 9.6 ms. the wtx field indicates the increase time factor to be used in this command execution (fdttemp = wtx * 9.6 ms). table 19. r-block detailed format b7-b6 b5 b4 b3 b2 b1 b0 0b10 1 x x 0 0 x r-block rfu 0: nak 1: ack 0: did field is not present 1: did field is present must be set to 0 rfu block number table 20. s-block format nfc frame sod eod pcb did payload crc length 1 byte 1 byte 0 to 1 byte 2 bytes 0xc2: for s(des) when the did field is not present 0xca: for s(des) when the did field is present 0xf2: for s(wtx) when the did field is not present 0xfa: for s(wtx) when the did field is present did field (optional) wtx field (1) 2 crc bytes 1. this field is present when b5-b4 bits are set to 0b11 (s-block is a wtx). see table 21: s-block detailed format . docid023790 rev 13 35/87 m24sr64-y i2c and rf command sets 76 note: after receiving the deselect command, the session is released and m24sr64-y enters the standby power mode. in i 2 c, the deselect command is executed only after the host has read the m24sr64-y deselect command response. in response to a rats command, m24sr64-y returns fwi parameter (default frame waiting time used); when m24sr64-y needs more time for a command execution, it requests a frame waiting time extension by responding 0xf2 0xwtx (request waiting time = fwi * wtx). if the reader accepts m24sr64-y reques t, it acknowledges by sending the command 0xf2 0xwtx. the frame waiting time becomes fwi * wtx for the current command only. 5.5 crc of the i 2 c and rf frame the two crc bytes check the data transmission be tween the rf host or i2c host and the m24sr64-y. for the rf frame, the crc is computed on all the data bits in the frame, excluding parity bits, sof and eof, and the crc itself. for the i2c frames, the crc is computed on all data bits of the frame excluding device select and the crc itself. the crc is as defined in iso/iec 13239. the initial register content shall be 0x6363 and the register content shall not be inverted after calculation. 5.6 nfc forum type 4 tag protocol 5.6.1 commands set with the nfc forum type 4 tag protocol, the commands are common to rf and i2c. table 21. s-block detailed format b7-b6 b5-b4 b3 b2 b1 b0 0b11 x x 0 1 0 s-block 0b00: deselect 0b11: wtx 0: did field is not present 1: did field is present - rfu rfu i2c and rf command sets m24sr64-y 36/87 docid023790 rev 13 5.6.2 status and error codes this section lists the status and the error code of the m24sr64-y. table 22. command set overview command name brief description ndef tag application select select the ndef tag application capability container select select the capability container (cc) file using the select command ndef select select the ndef file system file select select the system file readbinary read data from a file updatebinary write new data to a file table 23. status code of the m24sr64-y sw1 sw2 comment value 0x90 0x00 command completed successfully table 24. error code of the m24sr64-y sw1 sw2 comment length 1 byte 1 byte value 0x62 0x80 file overflow (le error) value 0x62 0x82 end of file or record reached before reading le bytes value 0x63 0x00 password is required value 0x63 0xcx password is incorrect, x further retries allowed (x can take value 0,1, 2) value 0x65 0x81 unsuccessful updating value 0x67 0x00 wrong length value 0x69 0x81 cmd is incompatible with the file structure value 0x69 0x82 security status not satisfied value 0x69 0x84 reference data not usable value 0x6a 0x80 incorrect parameters le or lc value 0x6a 0x82 file or application not found value 0x6a 0x84 file overflow (lc error) value 0x6a 0x86 incorrect p1 or p2 values docid023790 rev 13 37/87 m24sr64-y i2c and rf command sets 76 value 0x6d 0x00 ins field not supported value 0x6e 0x00 class not supported table 24. error code of the m24sr64-y (continued) sw1 sw2 comment length 1 byte 1 byte i2c and rf command sets m24sr64-y 38/87 docid023790 rev 13 5.6.3 ndef tag applic ation select command the rf or the i2c host shall send this command to activate the ndef tag application. to activate the ndef tag application, the rf host sends the select command (see table 25 ) in addition to the sequence define d in the nfc forum digital protocol. to activate the ndef tag application, the i2c host sends the select command (see table 25 ) in addition to the getsession or the kill rf session command. table 25 defines the c-apdu of the select command to select the ndef tag application (called ndef tag application select). table 26 defines the r-apdu of the ndef tag application select command. 5.6.4 capability cont ainer select command the rf or i2c host uses the capability contai ner select procedure to select the capability container (cc) file. the cc file is selected when this command re turns "command completed" in the r-apdu. table 27 defines the c-apdu of the se lect command to select the cc file (called capability container select). table 25. c-apdu of the ndef tag application select command name cla ins p1 p2 lc data le value 0x00 0xa4 0x04 0x00 0x07 0xd27600 00850101 0x00 class byte select instruction code p1 field p2 field number of bytes of data application id le field table 26. r-apdu of the ndef tag application select command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x6a 0x82 ndef tag application not found value - 0x6d 0x00 class not supported docid023790 rev 13 39/87 m24sr64-y i2c and rf command sets 76 table 28 defines the r-apdu of the cc select command. 5.6.5 ndef select command the rf or i2c host uses the ndef se lect command to select the ndef file. the ndef file is selected when this co mmand returns "command completed" in the r- apdu. table 29 defines the c-apdu of the select comma nd to select the ndef file (called ndef select). table 27. c-apdu of the capability container select command name cla ins p1 p2 lc data le value 0x00 0xa4 0x00 0x0c 0x02 0xe103 - class byte select instruction code p1 field p2 field number of bytes of data cc file id - table 28. r-apdu of the capability container select command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x6a 0x82 file or application not found value - 0x6d 0x00 class not supported table 29. c-apdu of th e ndef select command name cla ins p1 p2 lc data le value 0x00 0xa4 0x00 0x0c 0x02 0x000x - class byte select instruction code p1 field p2 field number of bytes of data 0x0001: first ndef file - i2c and rf command sets m24sr64-y 40/87 docid023790 rev 13 table 30 defines the r-apdu of the ndef select command. 5.6.6 system file select command the rf or i2c host uses this co mmand to select the system file. the system file is selected when this co mmand returns "command completed" in the r- apdu. table 31 defines the c-apdu of the command to se lect the system file (called system select). table 32 defines the r-apdu of the sy stem file select command. 5.6.7 readbinary command on receiving the readbinary command, the m24sr64-y reads the requested memory field and sends back its value in the r-apdu response. before sending a readbinary command, a file shall be selected by using a select command. table 30. r-apdu of the ndef select command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x6a 0x82 file or application not found table 31. c-apdu of the system file select command name cla ins p1 p2 lc data le 0x00 0xa4 0x00 0x0c 0x02 0xe101 - class byte select instruction code p1 field p2 field number of bytes of data system file id - table 32. r-apdu of the system file select command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x6a 0x82 capability container not found, no data is returned docid023790 rev 13 41/87 m24sr64-y i2c and rf command sets 76 the response of the readbinary command is su ccessful when the data to be read is within the selected file (a) ; in other words, when the sum of p1-p2 and le fields is equal to or lower than the selected file length. table 33 defines the readbinary command. table 34 defines the r-apdu of the readbinary command. 5.6.8 updatebinary command on receiving the updatebinary command, the m24sr64-y writes the data field into the selected file and sends back a status in the r- apdu response. if needed, m24srxx will request a timing extension (see section 5.4 ). before sending an updatebinary command, a file shall be selected by issuing a select command. table 35 defines the updatebinary command. a. for more details about cc file, refer to section 3.1.2: cc file layout . for more details about ndef file, refer to section 3.1.3: ndef file layout . for more details about system file, refer to section 3.1.4: system file layout . table 33. c-apdu of the readbinary command name cla ins p1 & p2 lc data le 0x00 0xb0 2 bytes - - 1 byte class byte read instruction code offset in the file selected - - number of bytes to read between 0x01 le max(selected file length, 0xf6) table 34. r-apdu of the readbinary command data sw1 sw2 comment length - 1 byte 1 byte - value content read 0x90 0x00 command completed value - 0x67 0x00 wrong length value - 0x69 0x82 security status not satisfied value - 0x6a 0x82 file or application not found value - 0x6e 0x00 class not supported i2c and rf command sets m24sr64-y 42/87 docid023790 rev 13 table 36 defines the r-apdu of the updatebinary command. note: for further return code s and definitions, refer to status and error codes . table 35. c-apdu of the updatebinary command name cla ins p1 & p2 lc data le 0x00 0xd6 2 bytes 1 byte lc bytes - class byte write instruction code offset in the file selected number of bytes of data (0x01 lc 0xf6) data to write in the m24sr64-y memory - table 36. r-apdu of the updatebinary command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x65 0x81 unsuccessful updating value - 0x67 0x00 wrong length value - 0x69 0x82 security status not satisfied value - 0x6a 0x82 file or application not found value - 0x6e 0x00 class not supported docid023790 rev 13 43/87 m24sr64-y i2c and rf command sets 76 5.7 iso/iec 7816-4 commands the iso/iec 7816-4 command set offers some ext ended features such as the protection of the ndef file. this command set is used to ma nage the right access of the ndef file. 5.7.1 verify command the verify command has two functions: 1. check if a password is required to access to the ndef file (the lc field = 0x00). 2. check that the password embedded in the verify command allows the access to the memory (the lc field = 0x10 and the password is present). when the lc field if equal to 0x00, the verify command returns a success code (0x90 00) provided that the access to the ndef file does not require a password. when the access to the ndef file is protected, the response to the verify command returns an error code (0x63 00). when the lc field equals 0x10, on receiving the verify command, the m24sr64-y compares the requested password with the data contained in the request and reports whether the operation has been successful in the response. before sending this command, an ndef file shall be selected by issuing the ndef select command. thus, this command checks the righ t access condition of the last ndef file selected. after a successful command, an access is granted for the whole ndef file. table 37 defines the verify command. table 37. verify command format name cla ins p1 & p2 lc data le 0x00 0x20 2 bytes 1 byte lc bytes - class byte instruction code password identification 0x0001: read ndef password transmit 0x0002: write ndef password transmit 0x0003: i2c password transmit (1) other: rfu 1. this code can only be issued by the i2c host. 0x00: the password is not present 0x10: the password is present in the data field password - i2c and rf command sets m24sr64-y 44/87 docid023790 rev 13 table 38 defines the r-apdu of the verify command. 5.7.2 change reference data command the change reference data command replaces the read or write password related to the ndef files previously selected. it can be perform ed only if the security status satisfies the security attributes for this command. before sending this command, the verify command with the correct ndef write password shall be issued. thus, this command changes the reference data of the ndef file. table 39 defines the change reference data command. table 39. change reference data command format table 38. r-apdu of the verify command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed, the password is correct value - 0x69 0x85 the conditions of use are not satisfied (e.g. no ndef file was selected) value - 0x69 0x81 cmd incompatib le with file structure value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 incorrect para meter in cmd data field value - 0x63 0x00 a password is required value - 0x63 0xcx (1) 1. at each session, the rf or i 2 c host can check a password 3 times. the password transmitted is incorrect and x encodes the number of further allowed retries. value - 0x6e 0x00 class not supported name cla ins p1 & p2 lc data le 0x00 0x24 2 bytes 1 byte lc bytes - class byte instruction code password identification 0x0001: read password transmit 0x0002: write password transmit 0x0003: i2c password transmit (1) other: rfu 1. this code can only be issued by the i2c host. 0x10: the password is present in the data field ndef file or i2c password - docid023790 rev 13 45/87 m24sr64-y i2c and rf command sets 76 table 40 defines the r-apdu of the change reference data command. 5.7.3 enable verification requirement command the enable verification requirement command activates the protection by password of the ndef file. when this command is successful, the read or write access to the ndef file is protected by a 128-bit password. it can be performed only if the security status satisfies the security attributes for this command. this command can update the right access of the ndef file by writing into the eeprom. in this case, the re sponse timing will be around 5 ms. before sending this command, the verify command with the correct ndef write password shall be issued. thus, this command chan ges the access right of the ndef file. table 41 defines the enable verification requirement command. the last five bits identify the pa ssword sent in the verify command. table 40. r-apdu of the chan ge reference data command data sw1 sw2 comment length 0 1 byte 1 byte - value - 0x90 0x00 command completed, the access right has been changed value - 0x69 0x81 cmd is incompatible with the file structure value - 0x65 0x81 unsuccessful updating value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 cc file or system file selected value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values value - 0x6e 0x00 class not supported table 41. enable verificati on requirement command format name cla ins p1 & p2 lc data le 0x00 0x28 2 bytes - - - class byte instruction code new security attributes 0x0001: enable the read prot ection of the ndef file 0x0002: enable the write protection of the ndef file other: rfu - - - i2c and rf command sets m24sr64-y 46/87 docid023790 rev 13 table 42 defines the r-apdu of the enable verification requirement command. 5.7.4 disable verification requirement command the disable requirement command deactivates the protection by password of the ndef file. when this command is succe ssful, the read or write access to the ndef file is granted without security requirements. it can be performed only if the security status satisfies the security attributes for this command. before sending this command, the verify command with the correct ndef write password shall be issued. thus, this command chan ges the access right of the ndef file. this command can update the right access of the ndef file by writing into the eeprom. in this case, the re sponse timing will be around 6 ms. table 43 defines the disable verification requirement command. table 44 defines the r-apdu of the disable verification requirement command. table 42. r-apdu of the enable verification requirement command data sw1 sw2 comment length 0 1 byte 1 byte - value - 0x90 0x00 command completed, the password is correct value - 0x69 0x81 cmd is incompat ible with the file structure value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 cc file or system file selected value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values table 43. disable verificati on requirement command format name cla ins p1 & p2 lc data le 0x00 0x26 2 bytes - - - class byte instruction code new security attributes 0x0001: disable the read prot ection of the ndef file 0x0002: disable the write protection of the ndef file other: rfu - - - docid023790 rev 13 47/87 m24sr64-y i2c and rf command sets 76 5.8 st proprietary command set the rf or i2c host can be issued with the command set described in this chapter. 5.8.1 extendedreadbinary command on receiving the extendedreadbinary comma nd, the m24sr64-y reads the requested memory field and sends back its value in the r-apdu response. before sending an extendedreadbinary command, a file shall be selected by issuing an ndef select command. the response of the extendedreadbinary comm and will be successful even if the data to be read is beyond the ndef message. the command returns an error code if the data to be read goes beyond the end of the file. table 46 defines the r-apdu of the read binary command. table 44. r-apdu of the disable verification requirement command data sw1 sw2 comment length 0 1 byte 1 byte - value - 0x90 0x00 command completed, the password is correct value - 0x69 0x81 cmd is incompatible with the file structure value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 cc file or system file selected value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values value - 0x6e 0x00 class not supported value - 0x65 0x81 update failed table 45. c-apdu of the extendedreadbinary command name cla ins p1 & p2 lc data le length 0xa2 0xb0 2 bytes - - 1 byte st class byte read instruction code offset in the file selected - - - number of bytes to read between 0x01 le 0xf6 i2c and rf command sets m24sr64-y 48/87 docid023790 rev 13 5.8.2 enablepermanentstate command the command configures the ndef file to the readonly or to the writeonly state. this command can update the right access to the ndef file by writing into the eeprom. in this case, the re sponse timing will be around 6 ms. table 47 defines the enablepermanentstate requirement command. table 48 defines the r-apdu of the enablepermanentstate command. table 46. r-apdu of the extendedreadbinary command data sw1 sw2 comment length le bytes 1 byte 1 byte - value content read 0x90 0x00 command completed value - 0x67 0x00 wrong length value - 0x69 0x82 security status not satisfied value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values value - 0x6e 0x00 class not supported table 47. enablepermanentstate command format name cla ins p1 & p2 lc data le length 0xa2 0x28 2 bytes - - - class byte instruction code new security attributes 0x0001: enable the read prot ection of the ndef file 0x0002: enable the write protection of the ndef file other: rfu - - - - table 48. r-apdu table of the enablepermanentstate command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x65 0x81 update failed value - 0x67 0x00 wrong length docid023790 rev 13 49/87 m24sr64-y i2c and rf command sets 76 5.8.3 disablepermanentstate command the command configures the ndef file to the lock state. this command can update the right access of the ndef file by writing into the eeprom. in this case, the respon se timing will be around 6 ms. th is command is only valid in i 2 c. the superuser rights must have been granted to execute the command. before sending this command, an ndef file shall be selected by issuing the ndef select command. table 49 defines the disablepermanentstate requirement command. table 50 defines the r-apdu of the disablepermanentstate command. value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 cc file or system file selected value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values value - 0x6e 0x00 class not supported table 48. r-apdu table of the enablepermanentstate command (continued) data sw1 sw2 comment table 49. disablepermanentstate command format name cla ins p1 & p2 lc data le length 0xa2 0x26 2 bytes - - - class byte instruction code new security attributes 0x0001: disable the read prot ection of the ndef file 0x0002: disable the write protection of the ndef file other: rfu - - - table 50. r-apdu of the disablepermanentstate command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x65 0x81 update failed value - 0x67 0x00 wrong length value - 0x69 0x82 security status not satisfied i2c and rf command sets m24sr64-y 50/87 docid023790 rev 13 5.8.4 updatefiletype command this command allows to modify the file type of a selected file to proprietary file (0x05) or ndef file (0x04). this command is granted only, when application and file are selected and if the file length and access right have previously been set to 0x00h (message invalid, all access rights granted). this command will update the file type located in the cc f ile by writing into the eeprom. in this case, the re sponse timing will be around 6 ms. table 51 defines the updatefiletype command. table 52 describes the r-apdu of the updatefiletype command. value - 0x6a 0x80 cc file or system file selected value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values value - 0x6e 0x00 class not supported table 50. r-apdu of the disablepermanentstate command (continued) data sw1 sw2 comment table 51. updatefiletype command format name cla ins p1 p2 lc data le value 0xa2 0xd6 0x00 0x00 0x01 0x04 or 0x05 - class byte select instruction code p1 field p2 field number of bytes of data file type - table 52. r-apdu of the updatefiletype command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 cc file or system file selected value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values docid023790 rev 13 51/87 m24sr64-y i2c and rf command sets 76 5.8.5 sendinterrupt command on receiving the sendinterrupt command, the m24sr64-y generates a negative pulse on the gpo pin. it starts at the end of the co mmand and ends at the end of the rf response. before sending this command, the system file shall be selected by issuing the system select command. table 53 defines the sendinterrupt command. table 54 describes the r-apdu of the sendinterrupt command. 5.8.6 statecontrol command on receiving the statecontrol command with re set value: data 0x00, the m24sr64-y drives the gpo pin low. on receiving the statecontr ol command with set value: data 0x01, the m24sr64-y releases the gpo pin which returns to hz. before sending this command, the system file shall be selected by issuing the system select command. table 55 defines the state control command. table 53. sendinterrupt command format cla ins p1&p2 lc data le length 1 byte 1 byte 2 bytes 1 byte - - value 0xa2 0xd6 0x001e 0x00 - - table 54. r-apdu of the sendinterrupt command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 the interrupt has been sent value - 0x6a 0x80 the gpo is not configured as an interrupt mode value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values value - 0x6e 0x00 class not supported table 55. statecontrol command format cla ins p1&p2 lc data le length 1 byte 1 byte 2 bytes 1 byte - - reset value 0xa2 0xd6 0x001f 0x01 0x00 - set value 0xa2 0xd6 0x001f 0x01 0x01 - i2c and rf command sets m24sr64-y 52/87 docid023790 rev 13 5.9 specific rf command set this section describes the command set that can be issued only by the rf host. 5.9.1 anticollision command set table 57 lists the commands that can be issued on ly by the rf host. the format of these commands is described in the nfc fo rum digital protocol specification. 5.9.2 rats comma nd and ats response rats command and ats response are used for nfc forum type 4a tag platform device activation (as defined in nfc foru m digital protocol specification). table 58 details the rats command. this command shall be se nt after the anticollision process. table 56. r-apdu of the statecontrol command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 the set or reset has been sent value - 0x6a 0x80 the gpo is not configured in statecontrol mode value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values value - 0x6e 0x00 class not supported table 57. commands issues by the rf host family command set comma nd name instruction code nfc-a technology all_req 0x52 (1) 1. code on 7 bits. sens_req 0x26 (1) sdd_req 0x93 or 0x95 or 0x97 sel_req 0x93 or 0x95 or 0x97 slp_req 0x50 docid023790 rev 13 53/87 m24sr64-y i2c and rf command sets 76 the fsdi field codes the fsd that defines the maximum size that an rf or i2c host is able to receive. table 59 gives the conversion from fdsi to fsd. the did field defines the value of the addressed m24sr64-y. the fsci codes the fsc which stands for the maximum frame size that the m24sr64-y is able to receive. the m24sr64-y is able to receive up to 256 bytes of command. if the rf or i2c host sends a command with more than 256 bytes, the m2 4sr64-y will not be able to treat the command and will not reply. the fwi which stands for the frame waiting time integer codes the fwt. this time corresponds to the maximum duration while an rf or i2c host shall send before sending the next command. table 58. rats command name ins param crc byte field 0xe0 1 byte 2 bytes bit field b7-b4 b3-b0 instruction code fsdi did (0 did 14) 2 crc bytes table 59. conversion from fdsi to fsd fsdi 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9h- 0xe 0xf fsd 16 24 32 40 48 64 96 128 256 rfu 256 table 60. ats response name tl t0 ta(1) tb(1) tc(1) crc byte field 0x05 0x78 1 byte 1 byte 0x02 2 bytes bit field b8-b5 b4-b1 length of the ats response fsci = 256 bytes the maximum ascending data rate is 106 kbps the maximum descending data rate is 106 kbps fwi field (9.6 ms when tb = 0x50) sfgi field (302 s when tb = 0x50) the did is supported 2 crc bytes i2c and rf command sets m24sr64-y 54/87 docid023790 rev 13 the sfgi which stands for the start-up fram e guard time is the minimum time that the reader shall wait after receiving the response of the m24sr64-y. 5.9.3 pps comm and & response pps (protocol and parameter se lection) command a nd response are defined in iso/iec 14443-4, in the protocol activation of picc type a. the pps command allows to change the data rates of the ascending (rf host to m24sr64- y) and descending (m24sr64-y to rf host) data rates. the ascending and descending data rates shall be coded as described in table 62 . when the m24sr64-y is able to change both da ta rates, it returns the following response. the data rate of this response is 106 kbps; then, the m24sr64-y changes the ascending and descending data rates. table 63 gives the details of the pps response. table 61. pps command - name ins pps0 pps1 crc byte field 0xdx 0x11 1 byte 2 bytes bit field b7-b4 b3-b0 0b0000 b3-b2 b1-b0 ins instruction code did pps1 is present pps1 rfu descending data rate ascending data rate 2 crc bytes table 62. ascending and descending data rate coding value 0b00 0b01 0b10 0b11 data rate 106 kbps rfu rfu rfu table 63. pps response name ins - pps0 byte field 0xdx - 0x11 bit field b8-b5 b4-b1 response code did field 2 crc bytes docid023790 rev 13 55/87 m24sr64-y i2c and rf command sets 76 5.10 specific i 2 c command set table 64 lists the commands that can only be issued by the i2c host. 5.10.1 geti2csession command the geti2csession command opens an i2c session if an rf session is not ongoing. table 65 defines the geti2csession command. the geti2csession command does not create a reply. when an rf session is ongoing, the m24srxx will not acknowledge the command. when no rf session is ongoing, the m24srx x will acknowledge the co mmand and open an i2c session. 5.10.2 killrfsession command the killrf session command closes the rf session and op ens an i2c session. table 66 defines the killrfsession command. the killrfsession command does not create a reply. the rf se ssion is closed when the device acknowledges the command. caution: a successful completion of the rf command is not certain. table 64. specific i 2 c commands command name format class byte instruction code brief description geti2csession - - 0x26 open an i 2 c session when the rf session is not ongoing killrfsession - - 0x52 kill the rf session and open an i 2 c session table 65. geti2csession command format ins length 1 byte value 0x26 table 66. killrfsession command format ins length 1 byte value 0x52 rf device operation m24sr64-y 56/87 docid023790 rev 13 6 rf device operation 6.1 anticollision and device acti vation command set for the rf interface the m24sr64-y device supports the command set defined in the nfc-a technology and the type 4a tag platform chapters of th e nfc digital protocol v1.0 specification. 6.2 open an rfsession once the rf host has terminated the ant icollision procedure and re trieve the at s response, it shall send the selectapplic ation command. the m24sr64-y will open an rf session. at this point, the rf host can send the app licative command set and the i2c cannot communicate with the m24sr64-y without cl osing first the rf session using the i 2 c killrfsession command. 6.3 close an rfsession the rf host can close the rf session by issuing one of these methods: ? send an s(des) command ? turn off the rf field 6.4 applicative command set the applicative command set is composed of the following command sets: ? the nfc forum type 4 tag command set ? the iso/iec 7816-4 command set ? the proprietary command set docid023790 rev 13 57/87 m24sr64-y i2c device operation 76 7 i 2 c device operation the m24sr64-y device supports the i 2 c protocol. the device that controls the data transfer is known as the bus master, and the other one as the slave device. a data transfer can only be initiated by the bus master, which also prov ides the serial clock for synchronization. the m24sr64-y device is a slave in all communications. 7.1 i 2 c communication protocol the i 2 c communication is built on a system of command and reply exchange. the i 2 c host starts the communication by sending a request. once a valid request is received by the m24sr64-y device, it carries out an internal operation and creates its answer. as defined in this documen t, and except for th e geti2c session an d kill rf session commands, the definition of a valid req uest is a command with a right crc value. figure 12 shows an exchange of a command and a response between the i2c host and the m24sr64-y. once the i2c session is open, the i2c host can send a command. the command is composed of: ? a device select field with the r/w bit set to 0. ? the command field. the m24sr64-y acknowledges on the reception of each byte. once the m24sr64-y is ready to send the answer, the i2c host shall: ? send a device select field with the r/w bit set to 1. ? release the sda line and send an scl clock. the i2c host shall acknowledge on the reception of each byte. figure 12. command and response exchange legend: s is the i 2 c start bit sequence p is the i 2 c stop bit sequence r/w is the 8 th bit of device select. note: a restart during a command and response exchange is not supported by the m24sr64-y. after a command, the i 2 c host can execute a polling se quence to determine when the response is available. polling sequence: loop on < start (s) + de viceselect with rw=0 + read nack/ack + stop (p) > the response is ava ilable as soon as the m24sr64- y sends an ack ( host read will a '0'). 0 6 9 ' h y l f h 6 h o h f w , & e x v & r p p d q g 6 3 ' h y l f h 6 h o h f w 5 h v s r q v h 6 3 5 : 5 : i2c device operation m24sr64-y 58/87 docid023790 rev 13 7.2 start condition a start condition is id entified by a falling edge of serial data (sda) while the serial clock (scl) is stable in the high state. a start co ndition must precede any data transfer command. the device continuously monitors (except duri ng an instruction processing) the sda and the scl for a start condition, and does not respond unless one is given. 7.3 stop condition a stop condition is identified by a rising ed ge of serial data (sda) while the serial clock (scl) is stable and driven high. a stop condit ion terminates a command between the device and the bus master. 7.4 i2c timeout on start condition i2c communication with the m24sr64-y starts with a valid start condition, followed by a device select code. if the delay between the start condition and the following rising edge of the serial clock (scl) that samples the most significan t of the device select exceeds the t start_out time, the i2c logic block is reset and further incoming data transfer is ignored until the next valid start condition. figure 13. i2c timeout on start condition 7.5 i2c timeout on clock period during a data transfer on the i2c bus, the serial clock high pulse width high ( t chcl ) or serial clock pulse width low ( t clch ) exceeds the maximum value specified in table 78 , the i2c logic block is reset and any furt her incoming data transfer is ignored until the next valid start condition. 0 6 9 6 & / 6 ' $ w 6 7 $ 5 7 b 2 8 7 6 w d u w f r q g l w l r q docid023790 rev 13 59/87 m24sr64-y i2c device operation 76 7.6 acknowledge bit (ack) the acknowledge bit is used to indicate a succ essful byte transfer. the bus transmitter, whether a bus master or a slave device, releas es the serial data (sda) after sending eight bits of data. during the 9th clock pulse period, the receiver pulls the sda low to acknowledge the receipt of the eight data bits. 7.7 data input during data input, the device samples serial da ta (sda) on the rising edge of the serial clock (scl). for a correct device operation, the sda must be stable during the rising edge of the scl, and the sda signal must change only when the scl is driven low. 7.8 i2c device address the device address is the concatenation of the group number coded on 4 bits and the i 2 c address coded on 3 bits, as shown in table 67 . 7.9 i2c frame format the i 2 c frame is composed of three fields: 1. sod field: contains the device select and the pcb. the pcb field is detailed in section 5.2 . 2. payload field: contains the command and its parameter, as defined in the i 2 c command set. 3. eod field: contains the two crc bytes computed on the sod but excluding the device select byte field. table 68 shows the format of an i 2 c frame. table 67. i 2 c device address format b7-b4b3b2b1b0 0b1010 1 1 0 0bx group number e2 bit e1 bit e0 bit 0 = request 1 = answer i2c device operation m24sr64-y 60/87 docid023790 rev 13 7.9.1 example of i2c frame commands ndef tag application command this example presents the i 2 c frame of an ndef tag applic ation select command. the i 2 c frame is detailed in table 69 . before sending a new command, the i 2 c host can send an i 2 c frame to read the m24sr64- y answer to the ndef tag application select command. figure 14 shows the i 2 c frame of the ndef tag application select command. table 68. i 2 c frame format i 2 c frame sod payload eod 0xac or 0xad 1 byte 1 to 251 bytes 2 bytes device select 0xac: to send a request to the m24sr64-y 0xad: to read a response of the m24sr64-y pcb field i 2 c command or i 2 c answer 2 crc bytes table 69. i 2 c host to m24sr64-y field sod payload eod value 0xac 0x02 or 0x03 command field 35 c0 or df be device select pcb field 0x00 a4 04 00 07 d2 76 00 00 85 01 01 00 2 crc bytes table 70. m24sr64-y to i 2 c host field sod payload eod i 2 c host to m24sr64-y m24sr64-y to i 2 c host value 0xad 0x02 or 0x03 0x90 00 f1 09 or 2d 53 device select pcb field i 2 c command 2 crc bytes docid023790 rev 13 61/87 m24sr64-y i2c device operation 76 figure 14. ndef tag application select command 7.10 open an i2c session to open an i2c session, the i2c host shall send either the getsession command or the killrfsession command. the getses sion command opens an i2c session if an rf session in not currently opened. a killrfsession command closes the current rf session if it exist and opens an i2c session. when an i2c session is opened, the rf host cannot communicate with the m24sr64-y and cannot close the i2c session. ?? 0 6 y 9 , e & e x v , e & e x v $ & . ? $ & . ? e $ & . $ & . % \ w h v h q w e \ w k h , e & k r v w ?e $ & . ? $ & . ? $ & . ? ? $ & . ? $ & . ? $ & . ? $ & . ??? $ & . ? $ & . ? $ & . [ $ & . [ & $ & . w xxx xxx ( q g r i w k h w u d q v p l v v l r q r i w k h u h t x h v w 6 w d u w r i w k h w u d q v p l v v l r q r i w k h u h t x h v w , e & e x v < ^ ?? < ?? < ? < ? & < ?? e} < xxx 6 w d u w r i w k h w u d q v p l v v l r q r i w k h d q v z h u $ & . $ f n q r z o h g j h e \ w k h , e & k r v w % \ w h v h q w e \ w k h 0 6 5 [ [ < w / h j h q g [ [ 6 6 w d u w v h q w e \ w k h , e & k r v w 3 6 w r s v h q w e \ w k h , e & k r v w v }( ?z ??v?u]??]}v }( ?z v? ? ? $ f n q r z o h g j h e \ 0 6 5 [ [ < [ $ & . ? 6 $ & . 1 r $ & . 1 r $ f n q r z o h g j h e \ w k h , e & k r v w % \ w h v h q w e \ w k h 0 6 5 [ [ < [ 3 6 w r s v h q w e \ w k h , e & k r v w i2c device operation m24sr64-y 62/87 docid023790 rev 13 7.11 close the i2c session there are three ways to close an i2c session: ? turn off the vcc power supply ? send the s(des) command and read the response ? wait for the i2c watchd og when it is enabled ? wait for the i2c timeout. docid023790 rev 13 63/87 m24sr64-y functional procedures 76 8 functional procedures this section describes some procedure to access the memory or manage its protection. 8.1 selection of an ndef message the rf or i2c host shall use this procedure to detect the ndef message inside an m24sr64-y. the ndef detection procedure is as follows: 1. open an rf or an i2c session 2. send the selectnd eftagapplication command 3. select the cc file 4. read the cc file 5. select the ndef file. 8.2 reading of an ndef message the rf or i2c host executes the ndef read procedure to read the ndef file. 1. detect successfully t he ndef file using the ndef detection procedure 2. check that the read access without any security is gr anted for the ndef file from the information provided by the cc file 3. select the ndef file 4. read the ndef file. 8.3 reading a locked ndef file the rf or i2c host executes this procedur e to read an ndef file which has been locked previously. 1. select the ndef tag application 2. select the ndef file 3. verify the read password by using the verify command 4. read the data in the ndef file. 8.4 locking an ndef file the rf or i2c host executes this procedure to protect an ndef file. 1. select the ndef tag application 2. check the right access provided by the cc file 3. select the ndef file 4. transmit the ndef file write password by using the verify command 5. lock the ndef file by sending the enable verification command. functional procedures m24sr64-y 64/87 docid023790 rev 13 8.5 unlocking an ndef file the rf or i2c host executes this procedure to read an ndef file which has been locked previously. 1. select the ndef tag application 2. select the ndef file 3. verify the ndef file write password or t he i2c password by using the verify command 4. unlock the ndef file by sending the disable verification command. 8.6 reaching the read-onl y state for an ndef file the rf or i2c host executes this procedure to read an ndef file which has been locked previously. 1. select the ndef tag application 2. select the ndef file 3. transmit the ndef file write password or the i2c password by using the verify command 4. send an enablepermanentstate command as the write access right of the previous select ndef file. 8.7 changing an ndef password procedure the rf or i2c host could use this procedure to change one ndef password. it can be a read or write password. 1. select the ndef tag application 2. select the ndef file 3. transmit the ndef file write password or the i2c password by using the verify command 4. change the password by sending a changereferencedata command. 8.8 changing a file type procedure the rf or i2c host executes this procedure to change the file type of a file for which all access rights were previously granted. 1. select the ndef tag application 2. select the file to be modified 3. set the file length to 0x00 using the updatebinary command 4. send an updatefiletype command with the new file type as data. docid023790 rev 13 65/87 m24sr64-y uid: unique identifier 76 9 uid: unique identifier the m24sr64-y is uniquely identified by a 7 bytes unique identifier (uid). the uid is a read-only code and comprises: ? the ic manufacturer code on 1 byte (0x02 for stmicroelectronics). ? the product code on 1 byte. ? a device number on 5 bytes. table 71 describes the uid format. table 71. uid format 0x02 0x84 or 0x8c (1) 1. automative grade 5 bytes ic manufacturer code m24sr64-y product code device number maximum rating m24sr64-y 66/87 docid023790 rev 13 10 maximum rating stressing the device ab ove the rating listed in table 72 may cause permanent damage to the device. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specif ication is not implied. exposure to absolute maximum rating conditions for extended periods may affect the device reliability. table 72. absolute maximum ratings symbol parameter min. max. unit t a ambient operating temperature -40 85 c t stg , h stg , t stg storage conditions sawn wafer on uv tape 15 25 c 6 (1) 1. counted from st shipment date. months kept in its original packing form t stg storage temperature ufdfpn8, so8, tssop8 ?65 150 c t stg storage temperature sawn bumped wafer (kept in its antistatic bag) 15 25 c storage time 6 months t lead lead temperature during soldering ufdfpn8, so8, tssop8 see note (2) 2. compliant with jedec std j-std-020d (for small body, sn-pb or pb assembly), the st ecopack ? 7191395 specification, and the european directive on restrictions on hazardous substances (rohs directive 2011/65/eu, july 2011). c v io i 2 c input or output range and gpo -0.50 6.5 v i cc (3) 3. based on characterization, not tested in producti on. maximum absorbed power = 100 mw @ 7.5 a/m rf supply current ac0 - ac1 - 100 ma v max_1 (3) rf input voltage amplitude between ac0 and ac1, gnd pad left floating vac0-vac1 - 10 v v max_2 (3) ac voltage between ac0 and gnd, or ac1 and gnd vac0-gnd or vac1-gnd -0.5 4.5 v v esd electrostatic discharge voltage (human body model) (4) 4. aec-q100-002 (compliant with jedec std jesd22-a114a, c1 = 100 pf, r1 = 1500 , r2 = 500 ) ac0-ac1 - 1000 v v esd electrostatic discharge voltage (human body model) (4) other pads - 3500 v docid023790 rev 13 67/87 m24sr64-y i2c dc and ac parameters 76 11 i 2 c dc and ac parameters this section summarizes the operating and measurement conditions, and the dc and ac characteristics of the device in i 2 c mode. the parameters in the dc and ac characteristic tables that follow are derived from tests performed under the measurement conditions summarized in the relevant tables. designers should check that the op erating conditions in their circuit match the measurement conditions when relying on the quoted parameters. figure 15. ac test measurement i/o waveform table 73. i 2 c operating conditions symbol parameter min. max. unit v cc supply voltage 2.7 5.5 v t a ambient operating temperature ?40 85 c table 74. ac test measurement conditions symbol parameter min. max. unit c l load capacitance 100 pf t r, t f input rise and fall times - 50 ns v hi-lo input levels 0.2 v cc to 0.8 v cc v v ref(t) input and output timing reference levels 0.3 v cc to 0.7 v cc v table 75. input parameters symbol parameter min. max. unit c in input capacitance (sda) - 8 pf c in input capacitance (other pins) - 6 pf t ns pulse width ignored (input filter on scl and sda) - 80 ns $ , & 9 & & 9 & & 9 & & 9 & & , q s x w d q g 2 x w s x w 7 l p l q j 5 h i h u h q f h / h y h o v , q s x w / h y h o v i2c dc and ac parameters m24sr64-y 68/87 docid023790 rev 13 table 76. i 2 c dc characteristics symbol parameter test condition min. max. unit i li input leakage current (scl, sda) v in = v ss or v cc device in standby mode - 2 a i lo output leakage current sda in hi-z, external voltage applied on sda: v ss or v cc - 2a i cc0 standby power mode supply current v cc = 3.3 v, with rf on - 30 a v cc = 3.3 v, with rf off - 5 v cc = 5.5 v, with rf on (1) - 30 v cc = 5.5 v, with rf off - 5 i cc1 supply current (i 2 c session open) v cc = 3.3 v, with rf on - 150 a v cc = 3.3 v, with rf off - 150 v cc = 5.5 v, with rf on - 150 v cc = 5.5 v, with rf off - 150 i cc2 supply current (2) (read binary) v cc = 3.3 v (f c = 1 mhz), with rf on (3) - 250 a v cc = 3.3 v (f c = 1 mhz), with rf off (3) - 200 v cc = 5.5 v (f c = 1 mhz), with rf on (3) - 250 v cc = 5.5 v (f c = 1 mhz), with rf off (3) - 200 i cc3 supply current (2) (update binary) v cc = 3.3 v (f c = 1 mhz), with rf on (3) - 550 a v cc = 3.3 v (f c = 1 mhz),with rf off (3) -500 v cc = 5.5 v (f c = 1 mhz), with rf on (3) - 550 v cc = 5.5 v (f c = 1 mhz), with rf off (3) -500 v il input low voltage (sda, scl) v cc = 2.7 v v cc = 5.5 v -0.45 0.3 v cc v v ih input high voltage (sda, scl) v cc = 2.7 v v cc = 5.5 v 0.7 v cc 6.5 v v il input low voltage (rf disable) v cc = 2.7 v v cc = 5.5 v - 0.45 v v ih input high voltage (rf disable) v cc = 2.7 v v cc = 5.5 v 1.4 -v v ol output low voltage (sda) i ol = 3 ma, v cc = 5.5 v - 0.4 v output low voltage (gpo) i ol = 1 ma, v cc = 2.7 to 5.5 v - 0.4 v 1. when an rf session is opened, i cc corresponds to the standby power mode. 2. characterized only. 3. input levels as defined in figure 15 . docid023790 rev 13 69/87 m24sr64-y i2c dc and ac parameters 76 table 77. i 2 c ac characteristics (400 khz) test conditions specified in table 73 (preliminary data based on design simulations) symbol alt. parameter min. max. unit f c f scl clock frequency 0.05 400 khz t chcl (1) 1. t chcl timeout. t high clock pulse width high 600 - ns t clch (2) 2. t clch timeout. t low clock pulse width low 1300 - ns t xh1xh2 t r input signal rise time (3) 3. there is no min. or max. value for the input signal rise and fall times. it is however recommended by the i2c specification that the input signal rise and fall times be more than 20 ns and less than 300 ns when f c < 400 khz. (3) ns t xl1xl2 t f input signal fall time (3) (3) ns t dl1dl2 t f sda (out) fall time 20 300 ns t dxcx t su:dat data in set up time 100 - ns t cldx t hd:dat data in hold time 0 - ns t clqx (4) 4. to avoid spurious start and stop conditions, a mini mum delay is placed between scl=1 and the falling or rising edge of sda. t dh data out hold time 100 - ns t clqv (5) 5. t clqv is the time (from the falling edge of scl) required by the sda bus line to reach 0.8v cc in a compatible way with the i 2 c specification (which specifies t su:dat (min) = 100 ns), assuming that the r bus c bus time constant is less than 500 ns (as specified in figure 17 ). t aa clock low to next data valid (access time) - 900 ns t chdx (6) 6. for a restart condition, or following a write cycle. t su:sta start condition set up time 600 - ns t dlcl t hd:sta start condition hold time 600 - ns t chdh t su:sto stop condition set up time 600 - ns t dhdl t buf time between stop condition and next start condition 1300 - ns t w t wr i2c write time in one page - 5 ms i2c write time up to 246 bytes - 150 ms t ns (7) 7. characterized only, not tested in production. - pulse width ignored (input filter on scl and sda) -80ns i2c dc and ac parameters m24sr64-y 70/87 docid023790 rev 13 table 78. i 2 c ac characteristics (1 mhz) test conditions specified in table 73 (preliminary data based on design simulations) symbol alt. parameter min. max. unit f c f scl clock frequency 0.05 1000 khz t chcl (1) 1. t chcl timeout. t high clock pulse width high 260 - ns t clch (2) 2. t clch timeout. t low clock pulse width low 500 - ns t xh1xh2 t r input signal rise time (3) 3. there is no min. or max. value for the input signal rise and fall times. it is however recommended by the i2c specification that the input signal rise and fall times be less than 120 ns when f c < 1 mhz. (3) ns t xl1xl2 t f input signal fall time (3) (3) ns t dl1dl2 t f sda (out) fall time 20 120 ns t dxcx t su:dat data in set up time 50 - ns t cldx t hd:dat data in hold time 0 - ns t clqx t dh data out hold time 100 - ns t clqv (4)(5) 4. to avoid spurious start and stop conditions, a mini mum delay is placed between scl=1 and the falling or rising edge of sda. 5. t clqv is the time (from the falling edge of scl) required by the sda bus line to reach 0.8v cc in a compatible way with the i 2 c specification (which specifies t su:dat (min) = 100 ns), assuming that the r bus c bus time constant is less than 500 ns (as specified in figure 17 ). t aa clock low to next data valid (access time) - 450 ns t chdx (6) 6. for a restart condition, or following a write cycle. t su:sta start condition set up time 250 - ns t dlcl t hd:sta start condition hold time 250 - ns t chdh t su:sto stop condition set up time 250 - ns t dhdl t buf time between stop condition and next start condition 500 - ns t w t wr i2c write time in one page - 5 ms i2c write time up to 246 bytes - 150 ms t ns (7) 7. characterized only, not tested in production. - pulse width ignored (input filter on scl and sda) -80ns docid023790 rev 13 71/87 m24sr64-y i2c dc and ac parameters 76 figure 16. i 2 c ac waveforms 11.1 i 2 c timing measur ement condition figure 17 represents the maximum rbus value vers us bus parasitic capacitance (cbus) for an i 2 c bus at maximum frequency f c = 400 khz. figure 17. maximum rbus value with f c = 400 khz 3 # , 3 $ ! ) n 3 # , 3 $ ! / u t 3 # , 3 $ ! ) n t # ( # , t $ , # , t # ( $ 8 3 t a r t c o n d i t i o n t # , # ( t $ 8 # 8 t # , $ 8 3 $ ! ) n p u t 3 $ ! # h a n g e t # ( $ ( t $ ( $ , 3 t o p c o n d i t i o n $ a t a v a l i d t # , 1 6 t # , 1 8 t # ( $ ( 3 t o p c o n d i t i o n t # ( $ 8 3 t a r t c o n d i t i o n 7 r i t e c y c l e t 7 ! ) e 3 t a r t c o n d i t i o n t # ( # , t 8 ( 8 ( t 8 ( 8 ( t 8 , 8 , t 8 , 8 , $ a t a v a l i d t $ , $ , a i b " u s l i n e c a p a c i t o r p & " u s l i n e p u l l u p r e s i s t o r k ) # b u s m a s t e r - x x x 2 b u s 6 # # # b u s 3 # , 3 $ ! 2 b u s # b u s n s ( e r e 2 b u s # b u s n s k ? p & 4 h e 2 x # t i m e c o n s t a n t m u s t b e b e l o w t h e n s t i m e c o n s t a n t l i n e r e p r e s e n t e d o n t h e l e f t b u s b u s i2c dc and ac parameters m24sr64-y 72/87 docid023790 rev 13 figure 18 represents the maximum rbus value vers us bus parasitic capacitance (cbus) for an i 2 c bus at maximum frequency f c = 1 mhz. figure 18. maximum rbus value with f c = 1 mhz figure 19. i 2 c bus protocol " u s l i n e c a p a c i t o r p & " u s l i n e p u l l u p r e s i s t o r k - 3 6 ) # b u s m a s t e r - x x x 2 b u s 6 # # # b u s 3 # , 3 $ ! ( e r e 2 b u s # b u s n s 2 b u s # b u s n s 4 h e 2 b u s # b u s t i m e c o n s t a n t m u s t b e b e l o w t h e n s t i m e c o n s t a n t l i n e r e p r e s e n t e d o n t h e l e f t 3 # , 3 $ ! 3 # , 3 $ ! 3 $ ! 3 4 ! 2 4 # o n d i t i o n 3 $ ! ) n p u t 3 $ ! # h a n g e ! ) " 3 4 / 0 # o n d i t i o n - 3 " ! # + 3 4 ! 2 4 # o n d i t i o n 3 # , - 3 " ! # + 3 4 / 0 # o n d i t i o n docid023790 rev 13 73/87 m24sr64-y i2c dc and ac parameters 76 table 79. device select code device type identifier (1) chip enable address rw b7 b6 b5 b4 b3 b2 b1 b0 device select code 1 0 1 0 1 1 0 rw 1. the most significant bit, b7, is sent first. gpo parameters m24sr64-y 74/87 docid023790 rev 13 12 gpo parameters this section lists the timing of the gpo according to its configuration. table 80. gpo timings measurement (1) gpo field i/f condition command symbol typ. unit session open 0xx1 i 2 c gpo low when session active kill session cmdstptogplow *add 100 s for boot after por 15* s get session 15* s i 2 c gpo return hz deselect answerlblbtogphz 105 ns 0x1x rf gpo low when session active ndef select cmdeoftogplow 170 s rf gpo return hz deselect cmdeoftogphz 370 s wip 0xx2 i 2 c gpo low when programming update binary cmdstptogplow 45 s i 2 c writing time duration (no time extension) 5ms rf gpo low when programming update binary cmdeoftogplow 75 s 0x2x rf writing time duration (no time extension) 5ms answer ready 0xx3 i 2 c gpo low when a command is computed readbinary or updatebinary cmdstptogplow 55 or 5 s ms i 2 c gpo return hz on new command all commands after newcmdlbfb or answerlbfb 105 ns message in progress 0x3x rf gpo low when modifying ndef updatebinary (msg length #0) cmdeoftogplow 75 s rf gpo low when modifying ndef updatebinary writing time duration (no time extension) 5ms interrupt 0xx4 i 2 c gpo low after receiving an interrupt command sendinterrupt cmdstptogplow 50 s i 2 c gpo return hz all commands after newcmdlbfb or answerlbfb 105 ns 0x4x rf gpo low after receiving an interrupt command sendinterrupt cmdeoftogplow 75 s rf pulse duration 540 s docid023790 rev 13 75/87 m24sr64-y gpo parameters 76 state control 0xx5 i 2 c gpo low when reset reset gpo cmdstptogplow 40 s i 2 c gpo return hz when set set gpo cmdstptogphz 40 s 0x5x rf gpo low when reset reset gpo cmdeoftogplow 60 s rf gpo return hz when set set gpo cmdeoftogphz 60 s rf busy 0x6x rf gpo low after receiving an rf command anticollision command or start of rf disturb (command using another rf protocol) cmdsoftogplow 6 s rf gpo return hz after deselection or rf command in another protocol deselect or end of rf disturb (command using another rf protocol) cmdeoftogphz 460 s 1. characterized only. table 80. gpo timings measurement (1) (continued) gpo field i/f condition command symbol typ. unit rf electrical parameters m24sr64-y 76/87 docid023790 rev 13 13 rf electrical parameters this section summarizes the operating and measurement conditions, and the dc and ac characteristics of the device in rf mode. the parameters in the dc and ac characterist ics tables that follow are derived from tests performed under the measurement conditi ons summarized in the relevant tables. designers should check that the operating cond itions in their circuit match the measurement conditions when relying on the quoted parameters. table 81. default operating conditions symbol parameter min. max. unit t a ambient operating temperature ?40 85 c table 82. rf characteristics (1) symbol parameter condi tion min typ max unit f c external rf signal freq uency 13.553 13.56 13.567 mhz h_iso operating field according to iso t a = 0 c to 50 c 1500 - 7500 ma/m h_extended operating field in extended temperature range t a = -40 c to 85 c 500 - 7500 ma/m mi carrier 100% carrier modulation index mi=(a-b)/(a+b) 90 - 100 % t 1 pause a length - 28/f c - 40.5/f c s t 2 pause a low time - 7/f c -t1s t 3 pause a rise time - 1.5xt4 - 16/f c s t 4 pause a rise time section - 0 - 6/f c s t min cd minimum time from carrier generation to first data from h-field min - - 5 ms w t rf write time (including internal verify) for one page --6-ms c tun internal tuning capacitor in so8 (2) f c = 13.56 mhz 22.5 25 27.5 pf t rf_off rf off time chip reset - - 5 ms 1. all timing characterizations were performed on a re ference antenna with the following characteristics: external size: 75 mm x 48 mm number of turns: 6 width of conductor: 0.6 mm space between two conductors: 0.6 mm value of the tuning capacitor in so8: 25 pf (m24sr64-y) value of the coil: 5 h tuning frequency: 14.2 mhz. 2. characterized only, at room temperature only, measured at vac0-vac1 = 2 v peak to peak at 13.56 mhz. docid023790 rev 13 77/87 m24sr64-y package mechanical data 83 14 package mechanical data in order to meet environmental requirements, st offers these devices in different grades of ecopack ? packages, depending on their level of environmental compliance. ecopack ? specifications, grade definitions a nd product status are available at: www.st.com . ecopack ? is an st trademark. 14.1 mechanical data for the so8n package figure 20. so8n - 8-lead pl astic small outline, 150 mils body width, package outline 1. drawing is not to scale. table 83. so8n - 8-lead plastic small out line, 150 mils body width, package data symbol millimeters inches (1) typ min max typ min max a - - 1.750 - - 0.0689 a1 - 0.100 0.250 - 0.0039 0.0098 a2 - 1.250 - 0.0492 b - 0.280 0.480 - 0.0110 0.0189 c - 0.170 0.230 - 0.0067 0.0091 ccc - - 0.100 - - 0.0039 d 4.900 4.800 5.000 0.1929 0.1890 0.1969 e 6.000 5.800 6.200 0.2362 0.2283 0.2441 e1 3.900 3.800 4.000 0.1535 0.1496 0.1575 e 1.270 - - 0.0500 - - h - 0.250 0.500 - - - k - 0 8 - 0 8 6 2 $ b 9 ( f f f e ' f ( k [ ? $ n p p / $ * $ 8 * ( 3 / $ 1 ( h $ / package mechanical data m24sr64-y 78/87 docid023790 rev 13 14.2 mechanical data for the tssop8 package figure 21. tssop8 - 8-lead thin shri nk small outline, package outline 1. drawing is not to scale. / l - 0.400 1.270 - 0.0157 0.0500 l1 1.04 - - 0.0410 - - 1. values in inches are converted from mm and rounded to 4 decimal digits. table 83. so8n - 8-lead plastic small out line, 150 mils body width, package data symbol millimeters inches (1) typ min max typ min max table 84. tssop8 - 8-lead thin shrink small outline, 169 mils width, package data symbol millimeters inches (1) typ min max typ min max a - - 1.200 - - 0.0472 a1 - 0.050 0.150 - 0.0020 0.0059 a2 1.000 1.800 1.050 0.0394 0.0315 0.0413 b - 0.190 0.300 - 0.0075 0.0118 c - 0.090 0.200 - 0.0035 0.0079 cp - - 0.100 - - 0.0039 d 3.000 2.900 3.100 0.1181 0.1142 0.1220 e 0.650 - - 0.0256 - - e 6.400 6.200 6.600 0.2520 0.2441 0.2598 e1 4.400 4.300 4.500 0.1732 0.1693 0.1772 l 0.600 0.450 0.750 0.02636 0.0177 0.0295 docid023790 rev 13 79/87 m24sr64-y package mechanical data 83 14.3 mechanical data for the ufdfpn8 package figure 22. ufdfpn8 - 8-lead ultra thin fine pitch dual flat package, no lead, 2x3 mm, package outline 1. drawing is not to scale. 2. the central pad (area e2 by d2 in the above illustration) is internally pulled to v ss . it must not be connected to any other voltage or signal line on the pcb, for example during the soldering process. l1 1.000 - - 0.0394 - - a08 08 n8 8 1. values in inches are converted from mm and rounded to 4 decimal digits. table 84. tssop8 - 8-lead thin shrink sm all outline, 169 mils width, package data symbol millimeters inches (1) typ min max typ min max = : b 0 ( h 9 > ? > ? >? w]v < 3 l q , ' p d u n l q j package mechanical data m24sr64-y 80/87 docid023790 rev 13 table 85. ufdfpn8 - 8- lead ultra thin fine pitch dual flat package, no lead, package data symbol millimeters inches (1) 1. values in inches are converted from mm and rounded to 4 decimal digits. typ min max typ min max a 0.550 0.450 0.600 0.0217 0.0177 0.0236 a1 0.020 0.000 0.050 0.0008 0.0000 0.0020 b 0.250 0.200 0.300 0.0098 0.0079 0.0118 d 2.000 1.900 2.100 0.0787 0.0748 0.0827 d2 (rev mc) - 1.200 1.600 - 0.0472 0.0630 e 3.000 2.900 3.100 0.1181 0.1142 0.1220 e2 (rev mc) - 1.200 1.600 - 0.0472 0.0630 e 0.500 - - 0.0197 - - k (rev mc) - 0.300 - - 0.0118 - l - 0.300 0.500 - 0.0118 0.0197 l1 - - 0.150 - - 0.0059 l3 - 0.300 - - 0.0118 - eee (2) 2. applied for exposed die paddle and terminals. exclude embedded part of exposed die paddle from measuring. - 0.080 - - 0.0031 - docid023790 rev 13 81/87 m24sr64-y package mechanical data 83 14.4 mechanical data for the wfdpn8 package figure 23. wfdfpn8 8-lead thin fine pitch dual flat package no lead package outline 1. drawing is not to scale. 2. the central pad (the area e2 by d2 in the above illustrat ion) must be either connected to vss or left floating (not connected) in the end application. table 86. wfdfpn8 8-lead thin fine pitch dual flat package no lead mechanical data symbol millimeters inches (1) min typ max min typ max a 0.7 0.75 0.8 0.0276 0.0295 0.0315 a1 0.025 0.045 0.065 0.001 0.0018 0.0026 b 0.2 0.25 0.3 0.0079 0.0098 0.0118 d 1.9 2 2.1 0.0748 0.0787 0.0827 e 2.9 3 3.1 0.1142 0.1181 0.122 e - 0.5 - - 0.0197 - l1 - - 0.15 - - 0.0059 l3 0.3 - - 0.0118 - - nx (2) 88 nd (3) 44 $ < b 0 ( b 9 7 r s y l h z 3 l q , ' p d u n l q j 6 l g h y l h z 6 h d w l q j s o d q h % r w w r p y l h z ' d w x p < 7 h u p l q d o w l s ' h w d l o 3 = 6 h h = ' h w d l o h h h / / / ( ( 1 ; e ' ' ( 1 ' [ h . h ' $ $ # & h ' d w x p < e e e g g g & & - - 3 l q $ % d d d # [ d d d # [ f f f # $ % h package mechanical data m24sr64-y 82/87 docid023790 rev 13 aaa 0.15 - - 0.0059 - - bbb 0.1 - - 0.0039 - - ccc0.1--0.0039-- ddd 0.05 - - 0.002 - - eee (4) 0.08 - - 0.0031 - - d2 1.05 - 1.65 0.0413 - 0.065 e2 1.05 - 1.45 0.0413 - 0.0571 k 0.45 - - 0.0177 - - l 0.3 - 0.5 0.0118 - 0.0197 1. values in inches are converted from mm and rounded to four decimal digits. 2. nx is the number of terminals. 3. nd is the number of terminals on "d" sides. 4. applied for exposed die paddle and terminals. ex cluding embedding part of exposed die paddle from measuring. table 86. wfdfpn8 8-lead thin fine pitch dual flat package no lead mechanical data (continued) symbol millimeters inches (1) min typ max min typ max docid023790 rev 13 83/87 m24sr64-y part numbering 83 15 part numbering note: parts marked as ?es?, ?e? or accompanied by an engineering sample notification letter, are not yet qualified and therefore not yet ready to be used in production and any consequences deriving from such usage will not be at st char ge. in no event, st wi ll be liable for any customer usage of these engineering samples in production. st quality has to be contacted prior to any decision to use these engineering samples to run qualification activity. table 87. ordering information scheme for packaged devices example: m24 sr 64- y mn 6 t /2 device type m24 = i 2 c interface device device feature sr = short range memory size 64 = memory size in kbits voltage range y = 2.7 to 5.5 v package mn = so8n dw = tssop8 mc = ufdfpn8 mf = wfdfpn8 (1) sb12i = 120 m 15 m bumped and sawn inkless wafer on 8-inch frame 1. package for automotive grade. device grade 6 = industrial: device tested with sta ndard test flow over ?40 to 85 c 7 = automotive 85 c : high releability test flow (2) (no parameter for sb12i) 2. preliminary data for automotiv e grade (under qualification). option t = tape and reel packing (no parameter for sb12i) capacitance /2 = 25 pf revision history m24sr64-y 84/87 docid023790 rev 13 16 revision history table 88. document revision history date revision changes 15-jan-2013 1 initial release. 12-apr-2013 2 global contents update. 16-may-2013 3 global contents update. 17-may-2013 4 updated ?number of bytes in cc file? value and comment in ta ble 4: cc file layout for 1 ndef file . added table 77: i2c ac characteristics (400 khz) and table 78: i2c ac characteristics (1 mhz) . 21-jun-2013 5 added missing ?tssop 8? below the second figure on page 1 . removed a sentence in section 1: functional description and updated a sentence in section 2.5: supply voltage (vcc) . updated section 2.7: general pu rpose output (gpo) including all graphics. updated section 3.1.2: cc file layout and section 3.2: read and write access rights to the memory , section 4.1: master and slave , section 4.2.2: i2c token , section 5.5: crc of the i2c and rf frame . added rows to table 6: field list . added a note to, updated table 8: details about the rf session field and table 10: details about the rf enable field . updated figure 1: see the procedure to lock the write access. and added a note below figure 12: command and response exchange . updated or added text to section 5.7.1: verify command to section 5.7.4: disable verification requirement command , section 8.7: changing an ndef password procedure updated table 62: ascending and descending data rate coding . added section 5.8: st proprietary command set , section 5.10: specific i2c command set and section 6: rf device operation changed ?getrfsession command into ?geti2csession command?, and ?detection of an ndef message? into ?selection of an ndef message?. updated iccs in table 76: i2c dc characteristics . removed ?ask modulated signal? figure and text before from section 13: rf electrical parameters . docid023790 rev 13 85/87 m24sr64-y revision history 86 29-aug-2013 6 added ufdfpn8 drawing on page 1 . changed ?dual interface device?, ?d ual interface eeprom? and ?dual interface memory? into ?n fc dynamic tag device?. changed ?enablepermanentsecurity? into ?enablepermanentstate? in table 13: rf and i2c command sets . updated the bitfields in ta ble 15 , table 19 , table 21 , ta ble 58 , table 61 and table 67 . changed the following commands: ? ?readmemory? into ?streadmemory?, ? ?read binary? into ?streadbinary?, ? ?enablepermanentlock? into ?enablepermanentstate?. updated i cc0 parameter in table 76: i2c dc characteristics and added a note. added section 14.3: mechanical data for the ufdfpn8 package and ufdfpn8 package. 08-nov-2013 7 global changes. 12-dec-2013 8 restored the whole content of table 76: i2c dc characteristics . updated the capacitor values in section 2.5.1: operating supply voltage vcc . removed bullet (4) from section 8.6: reaching the read-only state for an ndef file . updated v esd value in table 72: absolute maximum ratings , i cc values in table 76: i2c dc characteristics , and h_extended value in table 82: rf characteristics . added details to ?s(wtx)? bullet in section 5.4: s-block format . added sentences to section 5.6.8: updatebinary command and to section 5.8.3: disablepe rmanentstate command . changed ?0x001e? value into ?0x001f? in table 55: statecontrol command format . updated values in table 60: ats response . 18-dec-2013 9 changed the datasheet status from ?preliminary data? to ?production data?. added note (4) to figure 10: changing the read access right to an ndef file and figure 11: changing the write access right to an ndef file . table 88. document revision history (continued) date revision changes revision history m24sr64-y 86/87 docid023790 rev 13 17-feb-2014 10 updated figure 5: gpo configured as i2c answer ready (gpo field = 0xx3) and figure 8: gpo configured as state control (gpo field = 0xx5 or 0x5x) . added i 2 c text to the note below table 21: s-block detailed format . edited the third paragraph of section 5.8.1: extendedreadbinary command . added section 5.8.4: updatefiletype command and section 8.8: changing a file type procedure . updated bullet 3 in section 7.9: i2c frame format , and the payload row of table 69: i2c host to m24sr64-y . updated bullet 2 in section 7.11: close the i2c session . edited v io row and removed v esd (machine model) row from table 72: absolute maximum ratings . updated i cc rows and added a note to table 76: i2c dc characteristics . updated figure 20: so8n - 8-lead plastic small outline, 150 mils body width, package outline . fixed a typo in figure 22: ufdfpn8 - 8-lead ultra thin fine pitch dual flat package, no lead, 2x3 mm, package outline title: ufdpfn8 changed into ufdfpn8. 14-apr-2014 11 added wfdfpn8 package for automot ive grade under qualification added data for automotive grade in table 6: field list and table 71: uid format added figure 23: wfdfpn8 8-lead thin fine pitch dual flat package no lead package outline added table 86: wfdfpn8 8-lead thin fine pitch dual flat package no lead mechanical data added mf = wfdfpn8 inside table 87: ordering information scheme for packaged devices inserted byte <04> between a4 and 00 inside figure 14: ndef tag application select command 12-jun-2014 12 corrected las ndef user data address to 0x1ffc inside table 5: ndef file layout 05-jan-2015 13 updated figure 14: ndef tag application select command updated table 77: i2c ac characteristics (400 khz) added note after table 87: ordering information scheme for packaged devices table 88. document revision history (continued) date revision changes docid023790 rev 13 87/87 m24sr64-y 87 important notice ? please read carefully stmicroelectronics nv and its subsidiaries (?st?) reserve the right to make changes, corrections, enhancements, modifications, and improvements to st products and/or to this document at any time without notice. purchasers should obtain the latest relevant in formation on st products before placing orders. st products are sold pursuant to st?s terms and conditions of sale in place at the time of o rder acknowledgement. purchasers are solely responsible for the choice, selection, and use of st products and st assumes no liability for application assistance or the design of purchasers? products. no license, express or implied, to any intellectual property right is granted by st herein. resale of st products with provisions different from the information set forth herein shall void any warranty granted by st for such product. st and the st logo are trademarks of st. all other product or service names are the property of their respective owners. information in this document supersedes and replaces information previously supplied in any prior versions of this document. ? 2015 stmicroelectronics ? all rights reserved |
Price & Availability of M24SR64-YMC6T2
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |